Which versions of certificates-revocation-utils are malicious?

The following npm versions of certificates-revocation-utils are flagged malicious: 35.1.9. Treat any of these as compromised.

How do I remediate certificates-revocation-utils if I installed it?

Remove certificates-revocation-utils from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed certificates-revocation-utils — how do I know if it already compromised me?

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

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

Malicious package

certificates-revocation-utilsnpm

certificates-revocation-utils is a confirmed malicious npm package (MAL-2026-12539) that executes malicious code on install (malicious version 35.1.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in certificates-revocation-utils (npm)

MAL-2026-12539

Immediate action

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

npm uninstall certificates-revocation-utils

What this malware does

On module load, index.js requires vendor.js which fetches a platform-specific binary from runtime-reconstructed Cloudflare Workers hostnames (assembled via split-string concatenation such as ['oob-worker.','cf101-','adf.workers.','de','v'].join('')) with a DNS-TXT base64 chunked fallback resolved via *.dl.wel1.ru. The fetched bytes are written to a temp path with a randomized name, chmod 0755'd on POSIX, and executed via detached cp.spawn('/bin/sh',['-c', fp+' &'],{detached:true}) or cp.spawn('cmd.exe',['/c','start','/b',fp]). The download URL is not pinned, not hash-verified, and unrelated to the package's stated purpose ("shared utilities"). Additional obfuscation hides the child_process require and chmodSync call (require('child'+'process'), fs['chmod'+'Sync']), and a /tmp/.analytics_state stamp gates single-execution-per-TTL. Requiring or installing this package causes arbitrary attacker-controlled code to execute on the installer's machine.

Malicious versions

1 flagged

35.1.9

Indicators of compromise (SHA-256)

4f10384b425fd13237d69f5a9d71f6c893bd9063b32be2665f8a30f95ddda837

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for certificates-revocation-utils (version 35.1.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging certificates-revocation-utils across your stack and pipelines.
If you installed it — respond
Remove certificates-revocation-utils from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If certificates-revocation-utils 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 certificates-revocation-utils 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. certificates-revocation-utils on npm has been identified as a malicious package (version 35.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015240

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks certificates-revocation-utils-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