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

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

@years18/n8n-nodes-utils-helper-m is a confirmed malicious npm package (MAL-2026-13857) 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-m (npm)

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

What this malware does

The package's declared postinstall script (node callback.js) and its main entrypoint (index.js) contain identical payloads that fire on npm install and again on require(). The payload downloads a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/pyroxy.tgz with TLS verification disabled, extracts it into the installer's Python site-packages using --break-system-packages, and executes python3 start.py from /tmp/mhddos (the mhddos / PyRoxy DDoS tool). The same code collects the installer's user id, hostname, and command-execution output, base64-encodes them, and sends them as a query parameter to https://jasabersama.id/portfolio-data.php?k=S7k9xQ2mZj&c=..., again with rejectUnauthorized: false. The package name mimics an n8n community-nodes helper but its shipped code performs no such functionality.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

5db497bbce490daad792ade6e502a9d382634c48047a6be6fcf31fd731bf6a53

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-m (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-m across your stack and pipelines.

  2. If you installed it — respond

    @years18/n8n-nodes-utils-helper-m is a typosquat — you almost certainly intended a legitimately-named package. Remove @years18/n8n-nodes-utils-helper-m, 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-m 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-m 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-m 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-017401

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years18/n8n-nodes-utils-helper-m-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-m (npm) malicious package — MAL-2026-13857 | O3 Security