NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

create-wrangler-deploynpm

Advisory published Updated

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

Malicious code in create-wrangler-deploy (npm)

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

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

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.

Malicious versions

1 flagged
0.1.1

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb
c3bd71e3d5a93887188f34c9434d24b09d1108a2471ab437d6e78ae216162b05
f67431755cee00e8947e1b6818b548a5fe65566f23672b24b3281e730789f3e3

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for create-wrangler-deploy (version 0.1.1).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-008775GHSA-5pxw-jqgf-87rf

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks create-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.

Explore

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