@years18/n8n-nodes-utils-helper-rnpm
@years18/n8n-nodes-utils-helper-r is a confirmed malicious npm package (MAL-2026-13862) 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-r (npm)
What this malware does
@years18/n8n-nodes-utils-helper-r ships a postinstall script that, on npm install, downloads a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/pyroxy-full.tgz over TLS with certificate verification disabled and extracts it into the installer's Python site-packages directory, then verifies the drop by executing python3 start.py from /tmp/mhddos. The dropped payload is the PyRoxy / MHDDOS DDoS attack framework. The same postinstall collects the output of id and hostname, base64-encodes the result, and sends it via HTTPS GET (certificate verification disabled) to jasabersama.id/portfolio-data.php with a hardcoded key parameter. The package presents itself as an n8n community utility node, but the delivered payload is unrelated offensive tooling.
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-r (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-r across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-r 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-r 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-r 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-r-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.