@years19/n8n-nodes-utils-helper-vnpm
@years19/n8n-nodes-utils-helper-v is a confirmed malicious npm package (MAL-2026-13905) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @years19/n8n-nodes-utils-helper-v (npm)
What this malware does
The package's postinstall hook runs node callback.js, and package.json declares main: index.js with byte-identical contents, so the payload fires on both npm install and require()/import. On execution the code writes a Python UDP/TCP flood script to /tmp/attack.py and launches it via nohup python3 /tmp/attack.py &, directing ~650 threads at 103.118.252.21 on ports 80/443 for 600 seconds. In parallel, the code runs id and hostname, collects process/loadavg indicators, base64-encodes the result, and sends it via https.get with rejectUnauthorized: false to https://jasabersama.id/portfolio-data.php?k=S7k9xQ2mZj&c=<encoded>. Installer hosts become participants in an outbound DDoS attack while also leaking host identity to a hardcoded endpoint.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @years19/n8n-nodes-utils-helper-v (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @years19/n8n-nodes-utils-helper-v across your stack and pipelines.
If you installed it — respond
Remove @years19/n8n-nodes-utils-helper-v from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @years19/n8n-nodes-utils-helper-v was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @years19/n8n-nodes-utils-helper-v before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @years19/n8n-nodes-utils-helper-v-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.