Which versions of commonjs-assert are malicious?

The following npm versions of commonjs-assert are flagged malicious: 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate commonjs-assert if I installed it?

Remove commonjs-assert 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 commonjs-assert — how do I know if it already compromised me?

If commonjs-assert was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is commonjs-assert part of a known attack campaign?

Yes — commonjs-assert is associated with the IN-MAL-2026-010671, GHSA-hcmm-fvc7-pjv3, IN-MAL-2026-017285 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find commonjs-assert across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commonjs-assert (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commonjs-assert across your stack and pipelines.

Malicious package

commonjs-assertnpm

commonjs-assert is a confirmed malicious npm package (MAL-2026-10676) that executes malicious code on install (malicious versions 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in commonjs-assert (npm)

MAL-2026-10676

Immediate action

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

npm uninstall commonjs-assert

What this malware does

The package name resembles Node.js's built-in assert module. On require(), index.js spawns a detached node child process against lib/chai/utils/assertion.js. That file is a single-line obfuscator.io-style bundle (rotated string array, custom-base64 decoder, hex-indexed accessors) whose runtime behavior is to require http/https, perform an HTTP GET against a URL reconstructed from the encoded string array, and pass the response body to new Function(..., body)(require) — remote content fetched at import time and executed with Node's require available. The obfuscation hides the destination URL from static inspection and shields the network-to-eval sink. Any project that requires or imports this package silently triggers arbitrary remote code execution on the installer's host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.31.0.4

Indicators of compromise (SHA-256)

b7fa2454998144bffed3fc1e2d73046b8414179b59fb99d3339f2658e00637f7

02b1b90b34ceaca511acb3b1b2e4e16be4b3571613904788dcc379e7c40f9b6d

555e5576938d073c34738670ab1647ea3043120babe34a3815bf48e3c61625ad

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commonjs-assert (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commonjs-assert across your stack and pipelines.
If you installed it — respond
Remove commonjs-assert 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 commonjs-assert was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks commonjs-assert before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. commonjs-assert on npm has been identified as a malicious package (versions 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010671GHSA-hcmm-fvc7-pjv3IN-MAL-2026-017285

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks commonjs-assert-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