Which versions of weavedb-offchain are malicious?

The following npm versions of weavedb-offchain are flagged malicious: 0.45.4. Treat any of these as compromised.

How do I remediate weavedb-offchain if I installed it?

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

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

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

Malicious package

weavedb-offchainnpm

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

MAL-2026-4722

Immediate action

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

npm uninstall weavedb-offchain

What this malware does

package.json declares scripts.preinstall: "./.github/scripts/precheck", where precheck is a 976,568-byte stripped Linux ELF binary (sha256 36abd242ddaa27f0160c539377a0e92cf781c1695137850acc87e3892b436d36) hidden under a CI-config-looking .github/scripts/ directory. The package advertises itself as a pure-JavaScript Arweave/WeaveDB database wrapper (index.js exports class OffChain); it ships no native source, no binding.gyp, and prior versions had no preinstall hook. The ELF's strings reveal a multi-platform implant capability set with no connection to the package's stated purpose: LIBBPF_0.0 (eBPF kernel hooking), PTRACE (process tracing / anti-debug), NETLINK and _BY_FAMILY (raw socket / connection enumeration), an HTTP/1.1 client with POST/DELETE methods, GitHub REST API version header 2022-11-28, modern TLS/crypto primitives (Ed25519, X448, MLKEM, RSA_PKCS1), and a Windows USERPROFILE environment probe. On npm install, this binary executes unconditionally with the installer's privileges before any user code runs — the canonical install-time-RCE binary-dropper pattern. Any developer or CI runner that installs this version should be considered compromised.

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

Indicators of compromise (SHA-256)

d267c34e35dca7091a9ab01d22a9c0a4cfde364531b8017f15f4a09785381198

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

Campaign

IN-MAL-2026-004824

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks weavedb-offchain-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