Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

node-net-poolnpm

Advisory published Updated

node-net-pool is a confirmed malicious npm package (MAL-2026-15570) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-net-pool (npm)

MAL-2026-15570
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall node-net-pool

What this malware does

package.json declares a postinstall hook (node index.js) that runs automatically on npm install. The shipped index.js contains no networking or connection-pool code — the entire file body is a ~6.3KB numeric byte array (_s) decoded by a custom LCG+XOR routine (_d(a,k) using state p*0x41C64E6D+0x3039 & 0xFFFF XORed byte-wise) and passed directly to new Function(_d(_s,179))(), dynamically evaluating the decoded payload on the installer's machine at install time. The manifest advertises the package as 'Node.js network connection pool utilities' with main: index.js, but index.js exports nothing and only runs the obfuscated executor — the stated purpose does not match the shipped contents. Install-time evaluation of an opaque, obfuscated payload with no legitimate build-step justification, combined with the cover-story metadata, is a supply-chain dropper/RCE pattern.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

d24314418bdbb12ec2e84d2058ad3d10a0d281eb3fac01daf3a3e30335b51bae
d9c6bb87249429b2a3f3791589075bf872a433bd47a33b152f6809ccf94b1328

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for node-net-pool (version 1.0.0).

  2. If you installed it — respond

    Remove node-net-pool from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

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

Campaign

GHSA-vm9g-mp9v-6q5pIN-MAL-2026-019176

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks node-net-pool-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

node-net-pool (npm) malicious package — MAL-2026-15570 | O3 Security