{"id":"MAL-2026-16444","revision":"f8f3e0115718457bbad9caedfc0cef1b","records":[{"revision":"f8f3e0115718457bbad9caedfc0cef1b","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16444","aliases":[],"title":"Malicious code in n8n-nodes-healthmon (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (7b6e9b877fe50a6a5cdf3cd0af73e755973a6eecb2940424618a5edfdc9443ed)\nn8n-nodes-healthmon ships as a purported n8n health-monitoring node but its index.js binds an HTTP server on 0.0.0.0:41111 that reads a JSON body and passes the `c` field directly to child_process.exec, giving any network-reachable party arbitrary command execution on the installer's host. The listener is started with no authentication and no loopback restriction. package.json declares `postinstall: node postinstall.js || true`, and postinstall.js does `require('./index.js')`, so the listener launches automatically during `npm install` without user consent. The same code path also runs when n8n loads the node via dist/HealthMonNode.node.js, so re-exposure occurs on every n8n startup. The health-monitoring framing is a cover story; the actual behavior is a persistent, world-reachable backdoor.\n","state":0,"publishedAt":"2026-09-23T02:44:13+00:00","modifiedAt":"2026-09-23T03:00:06.2367111+00:00","affected":[{"ecosystem":"npm","name":"n8n-nodes-healthmon","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/n8n-nodes-healthmon/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16444","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16444","identifiers":["MAL-2026-16444"]},"retained":false,"historicalAffected":[]}],"coverage":[]}