Advisory

MAL-2026-10777

Also known as: None

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in n8n-nodes-probe (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (e9d1aeabd688ffe2fdb4206f6fc715413358a40ec3203ad213dc37bb123eaf62)
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.

Source: ossf-package-analysis (94cdde468d42a724e2306572a7154571d17dd65e247b426500874888862d5167)
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.

Severity

Not rated by the source.

Dates

Published
2026-07-17 13:26 UTC
Modified
2026-08-05 01:49 UTC

Affected packages and fixes

n8n-nodes-probe

npm · All systems

Affected

  • Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences