Which versions of cewe-npm-cops are malicious?

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

How do I remediate cewe-npm-cops if I installed it?

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

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

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

Malicious package

cewe-npm-copsnpm

cewe-npm-cops is a confirmed malicious npm package (MAL-2026-13438) that steals credentials and exfiltrates sensitive data (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cewe-npm-cops (npm)

MAL-2026-13438

Immediate action

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

npm uninstall cewe-npm-cops

What this malware does

[email protected] is a dependency-confusion probe. package.json declares scripts.preinstall = 'node preinstall.js'; preinstall.js reads os.hostname() and issues a dns.lookup against <hostname>.zfir3qor582xqvyqm0tdc7xpqgw7ky8n.oastify.com, an author-controlled Burp Collaborator (Interactsh) out-of-band host. Every npm install of this package unconditionally leaks the installer's machine hostname via DNS to a third-party OOB service. The package is otherwise hollow: version is set to 99.9.9 (max-version squat designed to override an internal package of the same name during resolution), main is an empty index.js, and author is the placeholder 'Your_HackerOne_Username'. The self-described 'harmless PoC' framing does not change the behavior: installer host identity is exfiltrated to an attacker-controlled endpoint at install time.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

673bd57ca8632e768772381c7439b0b15008914879dfb5c22d42e40ce954c9e5

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 cewe-npm-cops (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 cewe-npm-cops across your stack and pipelines.
If you installed it — respond
cewe-npm-cops 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 cewe-npm-cops 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 cewe-npm-cops 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. cewe-npm-cops 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-016668

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cewe-npm-cops-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