@years19/n8n-nodes-utils-helper-ynpm
@years19/n8n-nodes-utils-helper-y is a confirmed malicious npm package (MAL-2026-13908) 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-y (npm)
What this malware does
The package advertises itself as an n8n community utility helper node (package.json declares n8n.nodes: ["nodes/PwnNode.node.js"] with description 'Utility helper nodes for workflow automation'), but its callback.js (invoked from the declared postinstall hook node callback.js) and its main entry index.js contain identical top-level code that: (1) writes a Python script to /tmp/attack2.py and launches it via nohup python3 /tmp/attack2.py... &, which floods 103.118.252.21 on ports 80/443 with UDP/TCP traffic using 2000 threads for 900 seconds; and (2) collects host identity (uid, hostname, process/load information), base64-encodes it, and sends it over HTTPS GET to jasabersama.id/portfolio-data.php with TLS certificate verification disabled (rejectUnauthorized:false). Because the dropper is both in the postinstall script and at the top level of the main module, it executes on npm install and again every time a consumer requires the package or n8n loads the node.
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-y (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-y across your stack and pipelines.
If you installed it — respond
Remove @years19/n8n-nodes-utils-helper-y 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-y 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-y 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-y-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.