Which versions of common-roles are malicious?

The following npm versions of common-roles are flagged malicious: 99.1.0. Treat any of these as compromised.

How do I remediate common-roles if I installed it?

Remove common-roles from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed common-roles — how do I know if it already compromised me?

If common-roles was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find common-roles across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for common-roles (version 99.1.0).

Malicious package

common-rolesnpm

Advisory published May 1, 2026Updated May 12, 2026

common-roles is a confirmed malicious npm package (MAL-2026-3308) that executes malicious code on install (malicious version 99.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in common-roles (npm)

MAL-2026-3308

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall common-roles

What this malware does

The package common-roles was found to contain malicious code.

The OpenSSF Package Analysis project identified 'common-roles' @ 99.1.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.1.0

Indicators of compromise (SHA-256)

aec58e59cdd165705f080c8c63baf85d77c4f3b0bc9d1b781695cad976943df0

f602ee3e4db38c8befaab761a5f06c83f1a48c33822478a3ae25e315fcd337a2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for common-roles (version 99.1.0).
If you installed it — respond
Remove common-roles from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If common-roles was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. common-roles on npm has been identified as a malicious package (version 99.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks common-roles-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database