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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for node-net-pool (version 1.0.0).
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.
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
Campaign
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.