Which versions of weavedb-sdk-base are malicious?

The following npm versions of weavedb-sdk-base are flagged malicious: 0.21.1. Treat any of these as compromised.

How do I remediate weavedb-sdk-base if I installed it?

weavedb-sdk-base 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-sdk-base — how do I know if it already compromised me?

If weavedb-sdk-base 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-sdk-base part of a known attack campaign?

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

Malicious package

weavedb-sdk-basenpm

Malicious code in weavedb-sdk-base (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4724

Immediate action

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

npm uninstall weavedb-sdk-base

What this malware does

package.json declares "preinstall": "./bin/install-deps", pointing at a ~976KB packed Linux x86-64 ELF binary shipped in the tarball (sha256 36abd242ddaa27f0160c539377a0e92cf781c1695137850acc87e3892b436d36). The package self-describes as a pure-JavaScript decentralized-DB SDK, so a native Linux helper has no documented purpose during install. No source code (.c/.cc/.rs/binding.gyp), no node-gyp or prebuild-install machinery, and no hash/signature verification accompanies the binary; its bytes are packed (fragmented, non-contiguous strings characteristic of UPX or a custom packer), preventing review. Extracted strings reveal HTTP/1.1, POST, DELETE, https://, USERPROFILE, LIBBPF (eBPF), PTRACE, and TLS/cipher routines — capabilities entirely inconsistent with a JavaScript SDK and consistent with a credential-harvest / surveillance / RCE payload. On npm install weavedb-sdk-base on Linux, this binary executes with the installer's UID before dependency resolution completes, giving the publisher arbitrary native code execution on the installer's machine.

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

0.21.1

Indicators of compromise (SHA-256)

40b4b0c5f79c0370a77c3b559b70389ffee591aa22c76ca15c4077fe95b5078e

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

Campaign

IN-MAL-2026-004835

References

Credits

Amazon Inspector · finder

Detect & block this

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