weavedb-sdk-nodenpm
Malicious code in weavedb-sdk-node (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares "preinstall": "./dist/runtime.node", causing npm to execute a ~976 KB packed binary on every install. The file uses the .node extension typically reserved for Node.js native addons loaded via require()/process.dlopen, but here it is invoked directly as a shell command — not loaded as an addon. The binary is opaque (mostly non-ASCII, packed/obfuscated) and contains strings indicating HTTP networking (HTTP/1.1, POST, DELETE), environment-variable enumeration (USERPROFILE, PATH, LANG), TLS, and RSA/Ed25519 cryptography. There is no shipped source, no node-gyp/prebuild-install scaffolding, and no documented purpose for executing a binary at install. The combination of (a) lifecycle-hook execution of a shipped opaque binary, (b) misleading .node extension on a non-addon executable, and (c) embedded networking + env-scraping + crypto capability strings matches the dropper/credential-stealer fingerprint. On npm install, attacker-controlled code runs with the installer's privileges and has the capability to exfiltrate environment variables and credentials.
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 weavedb-sdk-node (version 0.45.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging weavedb-sdk-node across your stack and pipelines.
If you installed it — respond
weavedb-sdk-node 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-sdk-node 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-sdk-node 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 weavedb-sdk-node-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.