Which versions of debug-common are malicious?

Every published version of debug-common on npm is considered malicious. Remove the package entirely.

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

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

If debug-common 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 debug-common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for debug-common (all published versions).

Malicious package

debug-commonnpm

Advisory published Dec 1, 2025Updated Dec 1, 2025

debug-common is a confirmed malicious npm package (MAL-2025-191509) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in debug-common (npm)

MAL-2025-191509

Immediate action

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

npm uninstall debug-common

What this malware does

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

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

88f2a76a5ede2df04c7d9b90d9fe0164f99a388aaf4ba018dc9b40f2b794d967

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for debug-common (all published versions).
If you installed it — respond
Remove debug-common 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 debug-common 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. debug-common on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks debug-common-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