weavedb-warp-contracts-plugin-deploy

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. ## Source: google-open-source-security (146faaf0d97c6a533a969bc3f3f117811f9317dc865ed4ab37f1679842ddeaae) 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.