n8n-nodes-pwnnpm
n8n-nodes-pwn is a confirmed malicious npm package (MAL-2026-11004) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in n8n-nodes-pwn (npm)
What this malware does
The package's Pwn.node.js executes malicious code at module load time when n8n loads this community node. It opens a TCP socket to 10.0.0.145:4444 and pipes the socket to a spawned /bin/sh -i, giving a remote party interactive shell control of the installer's host. In parallel, top-level code runs host reconnaissance commands (network interfaces, routes, ARP, /proc/net/tcp, filesystem searches for flag/*.txt), reads /home/node/.n8n/database.sqlite (n8n's encrypted workflow credentials store) filtered for 'flag|password|secret', and reads /home/node/.n8n/config, POSTing the aggregated output to http://10.0.0.145:8000/rce-out3. The hardcoded 10.0.0.145 destination is a private RFC1918 address consistent with a lab/PoC target, but the payload is fully weaponized and would execute against any installer that loads the node.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for n8n-nodes-pwn (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging n8n-nodes-pwn across your stack and pipelines.
If you installed it — respond
n8n-nodes-pwn 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 n8n-nodes-pwn 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 n8n-nodes-pwn 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks n8n-nodes-pwn-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.