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

test-weavedb-sdknpm

Advisory published Updated

test-weavedb-sdk is a confirmed malicious npm package (MAL-2026-4690) that steals credentials and exfiltrates sensitive data (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-weavedb-sdk (npm)

MAL-2026-4690
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall test-weavedb-sdk

What this malware does

Package name impersonates the legitimate weavedb-sdk; lib/index.js is a near-verbatim copy of that SDK's Arweave/Warp/EthCrypto class so the package functions as a drop-in substitute. package.json declares "preinstall": "./dist/runtime.node", directly executing a 976KB opaque ELF on every npm install. The.node extension is deceptive — legitimate Node native addons are loaded via require()/dlopen, not spawned as standalone executables. Strings recovered from the binary include HTTP/1.1, POST, DELETE, https://, USERPROFILE, LIBBPF_0.0 (eBPF), PTRACE, Ed25519, and RSA_PKCS1_ — capabilities (HTTP egress, kernel-level eBPF, anti-debug ptrace, home-directory enumeration, cryptographic operations) consistent with an info-stealer / C2 implant and unrelated to the package's advertised purpose. The binary ships without source, build system, or any documentation, and runs unconditionally with the installer's privileges at install time.

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.1.1

Indicators of compromise (SHA-256)

e3bf1d859670570df6b5400c4ae762c8de880ada809bb4c371f32339744b8f9d
146faaf0d97c6a533a969bc3f3f117811f9317dc865ed4ab37f1679842ddeaae

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for test-weavedb-sdk (version 1.1.1).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-004829

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks test-weavedb-sdk-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

test-weavedb-sdk (npm) malicious package — MAL-2026-4690 | O3 Security