n8n-nodes-probenpm
Advisory published Updated
n8n-nodes-probe is a confirmed malicious npm package (MAL-2026-10777) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in n8n-nodes-probe (npm)
What this malware does
The package advertises itself as an n8n community-node utility but its main entry index.js executes a recon routine at module load. On require, it reads AWS, GCP, and Azure credential files, kubeconfig, the Kubernetes service-account token at /var/run/secrets/kubernetes.io/serviceaccount/token, SSH private keys and authorized_keys, and filters process.env for variables matching token/secret/key/password/aws/npm/github. It also collects hostname, uid/gid, network interfaces, /proc/net/route, /etc/resolv.conf, mounts, ps aux, /proc/1/cgroup, ARP table, and probes cloud instance metadata endpoints (169.254.169.254 and metadata.google.internal) and internal services (Docker API on 172.17.0.1:2375, K8s/GKE API on 10.0.42.16:6443, Jenkins). All collected data is POSTed to a hardcoded webhook.site endpoint. A shipped pkg_tmp.json carries an alternate package name (n8n-nodes-task-runner), consistent with republication of the same payload under multiple names. The MyNode.js stub is an empty n8n TaskRunner shell serving only as cover for the recon payload in index.js.
The OpenSSF Package Analysis project identified 'n8n-nodes-probe' @ 1.0.6 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for n8n-nodes-probe (7 malicious versions).
If you installed it — respond
n8n-nodes-probe is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If n8n-nodes-probe was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks n8n-nodes-probe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.