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

monadenpm

Advisory published Updated

monade is a confirmed malicious npm package (MAL-2026-4613) that steals credentials and exfiltrates sensitive data (malicious version 0.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in monade (npm)

MAL-2026-4613
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall monade

What this malware does

[email protected] advertises itself as a JavaScript monad/flow utility library (cjs/index.js exports flow, of, opt, ka, dev), yet ships a 976KB UPX-packed Linux x86-64 ELF at src/compiler/native and wires it directly to the npm preinstall lifecycle hook (package.json: "preinstall": "./src/compiler/native"). On every npm install on Linux, this opaque native binary executes with the installer's privileges before any of the package's JavaScript is even evaluated. The binary is deliberately obfuscated via UPX packing (signature "http://upx.sf.net" present in the file) and unpacked strings reveal HTTP client primitives (HTTP/1.1, POST, DELETE, XMLHttp), HTTPS URLs, environment-variable access, eBPF references, and anti-debug indicators — none of which are needed for a pure-JS utility library. The package ships no C/C++/Rust source, no binding.gyp, no build system; the binary is not the product of a compile step but a prebuilt opaque payload. This is the canonical install-time dropper shape: arbitrary attacker-controlled native code executed on the installer's machine on npm install, with cover-story naming ("compiler/native") that contradicts the package's advertised purpose.

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

Indicators of compromise (SHA-256)

32631bc0128011d7e526d2665460d2e4562c2d50602e38218e2ad3078635726a
146faaf0d97c6a533a969bc3f3f117811f9317dc865ed4ab37f1679842ddeaae

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for monade (version 0.0.7).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-004817

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks monade-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

monade (npm) malicious package — MAL-2026-4613 | O3 Security