Which versions of certificates-revocation-sw are malicious?

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

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

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

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

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

Malicious package

certificates-revocation-swnpm

certificates-revocation-sw is a confirmed malicious npm package (MAL-2026-12538) that steals credentials and exfiltrates sensitive data (malicious version 35.6.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in certificates-revocation-sw (npm)

MAL-2026-12538

Immediate action

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

npm uninstall certificates-revocation-sw

What this malware does

The package's index.js unconditionally loads bootstrap.js, which on require fetches a platform-specific binary from obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev and similar, assembled by joining split string fragments) with a DNS-TXT chunked-base64 fallback via *.dl.wel1.ru, writes it to /tmp or %TEMP% under disguised names (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. The package advertises itself as a certificate-revocation provider but contains no such functionality; the dropper is gated by cover-story env vars (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and mislabeled with 'telemetry'/'analytics' comments. Hostname obfuscation, disguised drop paths, detached execution, and the mismatch between advertised purpose and actual behavior indicate a deliberate remote-code-execution dropper against the installer's host.

Malicious versions

1 flagged

35.6.4

Indicators of compromise (SHA-256)

3037d3d739bf6d25fbb06a613915278de458d3b90547bdbf11b2710b7d88d82a

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

Campaign

IN-MAL-2026-015242

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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