@years19/n8n-nodes-utils-helper-unpm
@years19/n8n-nodes-utils-helper-u is a confirmed malicious npm package (MAL-2026-13904) 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-u (npm)
What this malware does
The package's postinstall hook (callback.js) and its declared main entry (index.js, byte-identical to callback.js) both write a Python script to /tmp/attack.py and spawn it via nohup python3 /tmp/attack.py... &. The script launches hundreds of UDP/TCP flood threads against the hardcoded target 103.118.252.21 for 600 seconds, turning the installer's host into a DDoS source against a third party. After launching the flood, the code collects host identifiers (id, hostname, running process count, /proc/loadavg), base64-encodes them, and issues an HTTPS GET to jasabersama.id/portfolio-data.php with query parameters k=S7k9xQ2mZj&c=<base64>, with TLS certificate verification disabled (rejectUnauthorized: false). Because index.js is the module's main entry, the same dropper also fires whenever the package is required — for example when loaded as an n8n community node — in addition to firing on npm install via the postinstall lifecycle hook.
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-u (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-u across your stack and pipelines.
If you installed it — respond
Remove @years19/n8n-nodes-utils-helper-u 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-u 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-u 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-u-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.