@years18/n8n-nodes-utils-helper-pnpm
@years18/n8n-nodes-utils-helper-p is a confirmed malicious npm package (MAL-2026-13860) 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 @years18/n8n-nodes-utils-helper-p (npm)
What this malware does
Package advertises itself as an n8n community utility-node helper but its postinstall hook (node callback.js) fetches two tarballs from jasabersama.id (mhddos.tgz and pyroxy.tgz) with TLS verification disabled, extracts them to /tmp and the Python user site-packages, installs network-attack Python dependencies via pip install --break-system-packages, and runs python3 start.py on the extracted MHDDoS code — turning the installer's host into a DDoS attack node. The same postinstall captures id and hostname output plus install progress, base64-encodes it, and sends it as a query parameter to https://jasabersama.id/portfolio-data.php (also with certificate verification disabled). The shipped node file is named nodes/PwnNode.node.js, contradicting the package's stated benign purpose.
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 @years18/n8n-nodes-utils-helper-p (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 @years18/n8n-nodes-utils-helper-p across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-p 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 @years18/n8n-nodes-utils-helper-p 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 @years18/n8n-nodes-utils-helper-p 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 @years18/n8n-nodes-utils-helper-p-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.