Malicious code in n8n-nodes-port-scanner (npm)
-= Per source details. Do not edit below this line.=-
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.
왜 이 VPI인가 (설명가능 · 실험적)
VPI 산정 기준
| 영향도(기본값(정보 없음)) | 55.00 |
| 악용 신호(추가 악용신호 없음) | ×1.00 |
| VPI | 55.00 |
VPI 공식 vpi-v1 기준