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

wrangler-deploynpm

Malicious code in wrangler-deploy (npm) Remove it immediately and rotate any exposed credentials.

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

What this malware does

The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.

Malicious versions

1 flagged
1.5.5

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wrangler-deploy (version 1.5.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wrangler-deploy across your stack and pipelines.

  2. If you installed it — respond

    wrangler-deploy 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 wrangler-deploy 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.

  4. How O3 protects you

    O3 blocks wrangler-deploy 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. wrangler-deploy on npm has been identified as a malicious package (version 1.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Detect & block this

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

wrangler-deploy (npm) malicious package — MAL-2026-5267 | O3 Security