Which versions of content-common are malicious?

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

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

content-common is a typosquat — you almost certainly intended a legitimately-named package. Remove content-common, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If content-common 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 content-common part of a known attack campaign?

Yes — content-common is associated with the IN-MAL-2026-016669 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 content-common 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 content-common (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging content-common across your stack and pipelines.

Malicious package

content-commonnpm

content-common is a confirmed malicious npm package (MAL-2026-13442) that typosquats a legitimate package to trick installs (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in content-common (npm)

MAL-2026-13442

Immediate action

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

npm uninstall content-common

What this malware does

[email protected] declares a preinstall lifecycle script in package.json that executes node -e to perform an HTTP GET to a unique subdomain of oastify.com (Burp Suite Collaborator): http://fyhmr907kt8qphysiu67m1p00r6iu8ix.oastify.com. This fires automatically on npm install, confirming arbitrary code execution on the installer's host and leaking the installer's public IP and DNS resolver metadata via the unique subdomain lookup to the attacker-controlled collaborator endpoint. The package's self-declared 'Mozilla bug bounty PoC' framing does not change the behavior: any consumer who installs this version triggers the out-of-band callback. The version number 99.9.9 is also consistent with a dependency-confusion / typosquat probe against an internal package name.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

5656ce6bbda8526587e40810d90b3188e11d507ebb13168203384bfac6b5ec1b

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for content-common (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging content-common across your stack and pipelines.
If you installed it — respond
content-common is a typosquat — you almost certainly intended a legitimately-named package. Remove content-common, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If content-common 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 content-common 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. content-common on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016669

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks content-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