n8n-nodes-port-scannernpm
n8n-nodes-port-scanner is a confirmed malicious npm package (MAL-2026-10998) that opens a backdoor for remote access (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-port-scanner (npm)
What this malware does
index.js executes a top-level IIFE at require-time that (1) runs hostname, hostname -I, id, ip route, ip neigh/arp and reads /etc/resolv.conf, opens a raw TCP socket to 103.27.109.184:8893, and writes the collected host identity and network configuration to that remote host; (2) spawns /bin/bash -i and pipes its stdin/stdout/stderr over a second TCP connection to 103.27.109.184:8893, granting the remote party an interactive shell on the installer's machine; and (3) enumerates internal subnets 172.17.0.0/24, 172.18.0.0/24, and 10.200.37.0/24 across ports 22, 80, 443, 3000, 5678, 8080, and 8443, including the open-port results in the exfil payload. The scanning behavior runs unconditionally when the module is loaded, against private networks the installer has not designated as targets, and its results are shipped to the same hardcoded bare-IP endpoint — the package's advertised 'port scanner' purpose is a cover for installer-side reconnaissance and remote access, not an operator-invoked pentest tool.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for n8n-nodes-port-scanner (3 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-port-scanner across your stack and pipelines.
If you installed it — respond
n8n-nodes-port-scanner establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If n8n-nodes-port-scanner 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-port-scanner 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-port-scanner-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.