Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

cloudflare_modulenpm

Advisory published Updated

cloudflare_module is a confirmed malicious npm package (MAL-2026-17768) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 3.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cloudflare_module (npm)

MAL-2026-17768
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cloudflare_module

What this malware does

Package [email protected] is a dependency-confusion lure targeting the cloudflare_* namespace. package.json declares scripts.postinstall: "node beacon.cjs", and beacon.cjs POSTs a JSON payload containing os.hostname(), the install path (__dirname), process.cwd(), and process.version to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plain HTTP. The package main (index.js) additionally calls require('./beacon.cjs').fire() at top level inside a try/catch, so the same host-identifier POST also fires whenever a downstream bundler or application require()s the package. The default export is a Proxy that returns a no-op for every property access, allowing bundlers that resolve an internal cloudflare_module name to complete the build cleanly so the beacon callback fires without producing errors. The package is published at version 99.0.1 with a generic "Compatibility shim." description, consistent with version-bumping to beat an internal registry during resolution. The README self-labels the package as an "authorized dependency-confusion test," but the beacon targets any machine that resolves the name — the installer never consents to the exfiltration — and the destination is an unattributed bare-IP collector, not infrastructure of the targeted namespace.

Malicious versions

4 flagged
1.0.01.0.13.0.099.0.1

Indicators of compromise (SHA-256)

0aeadec01dbc6c39254740f8f4557d53f8d7ab94136a4695525a70cd3f80d95d
14316e66f8d8eeb53b5fd4850537ac5398947feaf88f3837e39bfa587f60a0fb
351579deaec7e5f856dfe103fbc8b7979b0f746e8e058bc3c1d35a00556bedf0
f3a545e1e930894c3320e68c2aee17dd2cec7f20ed03b2e882905056d0eee242

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for cloudflare_module (4 malicious versions).

  2. If you installed it — respond

    cloudflare_module 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.

  3. Did it already run?

    If cloudflare_module was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. cloudflare_module on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021410IN-MAL-2026-021387IN-MAL-2026-021439IN-MAL-2026-021448

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks cloudflare_module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

cloudflare_module (npm) malicious package — MAL-2026-17768 | O3 Security