Which versions of carbon-monorepo are malicious?

The following npm versions of carbon-monorepo are flagged malicious: 20.1.1. Treat any of these as compromised.

How do I remediate carbon-monorepo if I installed it?

carbon-monorepo is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed carbon-monorepo — how do I know if it already compromised me?

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

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

Malicious package

carbon-monoreponpm

carbon-monorepo is a confirmed malicious npm package (MAL-2026-14229) that steals credentials and exfiltrates sensitive data (malicious version 20.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in carbon-monorepo (npm)

MAL-2026-14229

Immediate action

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

npm uninstall carbon-monorepo

What this malware does

The package's package.json declares a postinstall hook that runs index.js on npm install. index.js collects host reconnaissance and installer secrets — os.hostname(), full process.env, platform/arch, cwd, package.json, node_modules listing, and the output of shell commands whoami/uname/id/cat /etc/passwd/cat /etc/shadow — and reads ~/.npmrc (which typically contains npm auth tokens) and recent ~/.npm/_logs. The collected data is POSTed over plain HTTP via http.request to the hardcoded host ywy8qnd4a931ga4v74k70b9g67c00qof.oastify.com, a Burp Collaborator (OAST) subdomain. Package metadata masquerades as an esbuild netbsd-x64 build ("description": "netbsd-x64 build for esbuild") but the tarball ships only the recon/exfil script, no build artifacts or library code — the sole install-time effect is running the exfiltration payload.

Malicious versions

1 flagged

20.1.1

Indicators of compromise (SHA-256)

9c617e93833344e13d376182fb00c13994a4d2e7f3f8220998e541d77a8e8713

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for carbon-monorepo (version 20.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging carbon-monorepo across your stack and pipelines.
If you installed it — respond
carbon-monorepo is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If carbon-monorepo 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 carbon-monorepo 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. carbon-monorepo on npm has been identified as a malicious package (version 20.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018329

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks carbon-monorepo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database