warp-contracts-plugin-deploy-testnpm
Malicious code in warp-contracts-plugin-deploy-test (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package name warp-contracts-plugin-deploy-test mimics the legitimate warp-contracts-plugin-deploy and copies its public API surface (lib/cjs/index.js re-exports DeployPlugin, CreateContractImpl, SourceImpl, Arweave/Ethereum signers identical to the genuine package). package.json declares "preinstall": "./bin/install-deps" where bin/install-deps is a 976,568-byte packed Linux ELF binary (sha256 36abd242ddaa27f0160c539377a0e92cf781c1695137850acc87e3892b436d36). The package self-describes as a TypeScript Warp Contracts deploy plugin — there is no native source tree, no node-gyp/binding.gyp, no documented purpose for shipping a Linux ELF helper. Readable strings in the binary (LIBBPF, PTRACE, NETLINK_DIAG, HTTP/1.1, https://, USERPROFILE) are inconsistent with any deploy-plugin function and consistent with a host-implant payload. On npm install, the binary runs with the installer's privileges, executing attacker-supplied compiled code that the scanner cannot inspect.
This package was compromised as part of the IronWorm campaign. This campaign executes a malicious binary payload during installation via a preinstall hook. The payload is a Rust-built infostealer that targets developer environments, scanning for and harvesting credentials related to cloud providers, object storage, databases, source-control, package registries, and AI developer tools. It also targets cryptocurrency wallets, specifically injecting a malicious JavaScript hook into the Exodus desktop wallet to capture passwords and recovery phrases. Furthermore, the malware exhibits worm-like behavior by stealing GitHub and NPM credentials to push malicious updates to the victim's repositories and publish trojanized packages, and it uses an eBPF-based kernel rootkit to hide its processes and network connections on Linux systems.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for warp-contracts-plugin-deploy-test (version 3.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging warp-contracts-plugin-deploy-test across your stack and pipelines.
If you installed it — respond
warp-contracts-plugin-deploy-test 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 warp-contracts-plugin-deploy-test 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 warp-contracts-plugin-deploy-test 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks warp-contracts-plugin-deploy-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.