Which versions of weavedb-warp-contracts-plugin-deploy are malicious?

The following npm versions of weavedb-warp-contracts-plugin-deploy are flagged malicious: 1.0.11. Treat any of these as compromised.

How do I remediate weavedb-warp-contracts-plugin-deploy if I installed it?

weavedb-warp-contracts-plugin-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 weavedb-warp-contracts-plugin-deploy — how do I know if it already compromised me?

If weavedb-warp-contracts-plugin-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 weavedb-warp-contracts-plugin-deploy part of a known attack campaign?

Yes — weavedb-warp-contracts-plugin-deploy is associated with the IN-MAL-2026-004838 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 weavedb-warp-contracts-plugin-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 weavedb-warp-contracts-plugin-deploy (version 1.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging weavedb-warp-contracts-plugin-deploy across your stack and pipelines.

Malicious package

weavedb-warp-contracts-plugin-deploynpm

Malicious code in weavedb-warp-contracts-plugin-deploy (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4727

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall weavedb-warp-contracts-plugin-deploy

What this malware does

package.json declares "preinstall": "./tools/setup", which is a 976 KB Linux x86_64 ELF binary shipped in the tarball with no source, no build system, and no documentation. The README describes a pure-TypeScript Warp Contracts deploy plugin and contains no mention of a native helper — there is no legitimate reason for this package to execute an opaque native binary on every npm install. The shipped ELF contains strings consistent with a credential harvester: an HTTP/1.1 client, USERPROFILE/HOME environment reads, libbpf and PTRACE process-inspection capabilities, and X25519/Ed25519 cryptographic primitives. The package name weavedb-warp-contracts-plugin-deploy impersonates the legitimate warp-contracts-plugin-deploy published by warp.cc, and the README is copied verbatim from the legitimate package (linking to academy.warp.cc) despite this package being published under neither warp.cc nor an official WeaveDB scope. The combination of a typosquat-style lure with a documentation-mismatched native dropper auto-executed at install time is an unambiguous supply-chain attack: any developer who runs npm install against this package executes attacker-controlled native code with the user's privileges before any other code review can occur.

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

1 flagged

1.0.11

Indicators of compromise (SHA-256)

a98f87e329831590a7416ca47a949a7b21cf8e948491e875d8359ca8d5cc5959

146faaf0d97c6a533a969bc3f3f117811f9317dc865ed4ab37f1679842ddeaae

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 weavedb-warp-contracts-plugin-deploy (version 1.0.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging weavedb-warp-contracts-plugin-deploy across your stack and pipelines.
If you installed it — respond
weavedb-warp-contracts-plugin-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 weavedb-warp-contracts-plugin-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 weavedb-warp-contracts-plugin-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. weavedb-warp-contracts-plugin-deploy on npm has been identified as a malicious package (version 1.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004838

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks weavedb-warp-contracts-plugin-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