Which versions of wrangler-deploy are malicious?

The following npm versions of wrangler-deploy are flagged malicious: 1.5.5. Treat any of these as compromised.

How do I remediate wrangler-deploy if I installed it?

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.

I already installed wrangler-deploy — how do I know if it already compromised me?

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.

Is wrangler-deploy part of a known attack campaign?

Yes — wrangler-deploy is associated with the IN-MAL-2026-008651 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 wrangler-deploy 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 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.

Malicious package

wrangler-deploynpm

wrangler-deploy is a confirmed malicious npm package (MAL-2026-5267) that steals credentials and exfiltrates sensitive data (malicious version 1.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wrangler-deploy (npm)

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

Package name wrangler-deploy is close to Cloudflare's official wrangler CLI, which raises confusion-risk concerns for developers who may install it expecting an official Cloudflare tool. Pattern-based signals fired on dist/cli/index.js, dist/core/dev-ui.js, dist/core/runtime.js, dist/core/sandbox-proxy.js, and dist/core/crypto.js based on co-occurrence of keywords like ping, POST/GET, Buffer.from(..., 'base64'), and hostname in minified/bundled code. These keyword patterns are consistent with a Wrangler-shaped CLI (HTTP requests to Cloudflare APIs, dev server, base64 token handling) but cannot be conclusively distinguished from exfiltration patterns without semantic verification of the bundled code. No specific attacker-controlled endpoint, credential-harvest path, install-time lifecycle hook, or dropper has been identified. Routing to human review to verify whether the package is a legitimate Cloudflare-adjacent tool, an unofficial deploy wrapper, or a name-confusion squat with hidden behavior in the minified bundles.

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

0d2085fa4916157b99799df085aa11e3d29bdb9a47f5798c85375b1bfdf8bd7e

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

Campaign

IN-MAL-2026-008651

References

Credits

Amazon Inspector · finder

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database