Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@years18/n8n-nodes-utils-helper-snpm

@years18/n8n-nodes-utils-helper-s is a confirmed malicious npm package (MAL-2026-13863) that typosquats a legitimate package to trick installs (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-s (npm)

MAL-2026-13863
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @years18/n8n-nodes-utils-helper-s

What this malware does

The package's postinstall lifecycle script downloads two tarballs (mhddos.tgz, pyroxy.tgz) from jasabersama.id over an HTTPS connection with TLS verification disabled (rejectUnauthorized:false), extracts them to /tmp and into the Python user site-packages, pip-installs a fixed dependency set with --break-system-packages, and immediately runs python3 start.py from the extracted mhddos directory. In parallel, it collects the output of id and hostname plus install-progress markers, base64-encodes them, and sends them as a query-string parameter to https://jasabersama.id/portfolio-data.php with a fixed key S7k9xQ2mZj. The payload URL is staged under a .theme-backup/dl/ cover-story path on a domain unrelated to the package's declared purpose, and the package's n8n node file is a stub — the sole functional code is the malicious postinstall. The name mimics legitimate n8n community node packages.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

791cd15471cd2592323fdd5d9b58f79903e29a77b73384d0fd8b1bc7b4b43342

Detection & response playbook

Typosquat

  1. Find 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-s (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-s across your stack and pipelines.

  2. If you installed it — respond

    @years18/n8n-nodes-utils-helper-s is a typosquat — you almost certainly intended a legitimately-named package. Remove @years18/n8n-nodes-utils-helper-s, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If @years18/n8n-nodes-utils-helper-s 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.

  4. How O3 protects you

    O3 blocks @years18/n8n-nodes-utils-helper-s 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

No. @years18/n8n-nodes-utils-helper-s on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017394

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years18/n8n-nodes-utils-helper-s-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@years18/n8n-nodes-utils-helper-s (npm) malicious package — MAL-2026-13863 | O3 Security