wrangler-deploynpm

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

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.