{"id":"MAL-2026-13907","revision":"7d50ec4cefd145c18c98413643def2ae","records":[{"revision":"7d50ec4cefd145c18c98413643def2ae","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13907","aliases":[],"title":"Malicious code in @years19/n8n-nodes-utils-helper-x (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (da3601885350a7fc85f418da9fb3f800a5e76949562ad23ac44d5c2b068088c4)\nThe package's postinstall hook runs node callback.js, and package.json declares main=index.js which is byte-identical to callback.js, so both npm install and require() of the package execute the same payload. The payload writes /tmp/attack2.py — a threaded UDP/TCP flood loop targeting 103.118.252.21 for 900 seconds — and launches it via `nohup python3 /tmp/attack2.py &`, weaponizing the installer's host and IP as a DDoS bot. In parallel, it collects the output of `id`, `hostname`, a process check and /proc/loadavg, base64-encodes it, and sends it over HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized:false). The package is presented as an n8n utility helper but ships no such functionality; its only observable behavior is the DDoS launcher and host-identity beacon.\n","state":0,"publishedAt":"2026-08-12T15:07:41+00:00","modifiedAt":"2026-08-12T15:30:13.3848129+00:00","affected":[{"ecosystem":"npm","name":"@years19/n8n-nodes-utils-helper-x","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@years19/n8n-nodes-utils-helper-x/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13907","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13907","identifiers":["MAL-2026-13907"]},"retained":false,"historicalAffected":[]}],"coverage":[]}