Which versions of cccmyssr3 are malicious?

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

How do I remediate cccmyssr3 if I installed it?

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

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

Yes — cccmyssr3 is associated with the IN-MAL-2026-007438 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 cccmyssr3 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 cccmyssr3 (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 cccmyssr3 across your stack and pipelines.

Malicious package

cccmyssr3npm

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

MAL-2026-6392

Immediate action

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

npm uninstall cccmyssr3

What this malware does

On npm install, this package automatically runs postinstall.js, which executes curl -X POST with a body containing the installer's hostname ($(hostname)), current user ($(whoami)), and the first 10 environment variables base64-encoded ($(env | head -10 | base64 -w 0)), sending them over plain HTTP to http://r1x55270.requestrepo.com — a requestrepo.com subdomain used as an attacker data-collection endpoint. Environment variables on developer and CI machines routinely contain credentials, API tokens, and CI secrets, so this is a credential-theft payload. The package's main is a trivial one-line formatDate stub and its description is 'A harmless utility package' — a cover story unrelated to the lifecycle behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a15e77975be346fa9b834e50124784a6774b5385e47072ae80911f5eda92cabf

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 cccmyssr3 (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 cccmyssr3 across your stack and pipelines.
If you installed it — respond
cccmyssr3 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 cccmyssr3 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 cccmyssr3 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. cccmyssr3 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-007438

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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