@years19/n8n-nodes-utils-helper-tnpm
@years19/n8n-nodes-utils-helper-t is a confirmed malicious npm package (MAL-2026-13903) that steals credentials and exfiltrates sensitive data (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-t (npm)
What this malware does
The package's postinstall script (callback.js) and its main entry point (index.js, byte-identical) execute automatically on npm install and on require()/import. They write a Python UDP/TCP flood script to /tmp/attack.py and launch it via nohup python3 /tmp/attack.py... & targeting the hardcoded IP 103.118.252.21 for 600 seconds, turning the installer host into a DDoS participant. In parallel, they collect the output of id and hostname along with process and loadavg data, base64-encode it, and send it via https.get to https://jasabersama.id/portfolio-data.php with TLS certificate verification disabled (rejectUnauthorized: false). The package is presented as an n8n utility node, but its actual behavior is remote code execution against a third-party target combined with installer host-identity exfiltration.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-t (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-t across your stack and pipelines.
If you installed it — respond
@years19/n8n-nodes-utils-helper-t is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @years19/n8n-nodes-utils-helper-t 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-t 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-t-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.