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

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

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

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

What this malware does

The package's postinstall script and its main entry (index.js, byte-identical to callback.js) execute the same payload on npm install and on require(). The payload runs id and hostname, base64-encodes the output, and sends it to https://jasabersama.id/portfolio-data.php with k= and c= query parameters; TLS certificate verification is disabled (rejectUnauthorized:false). The c= parameter carries a base64-decode-and-append shell command written to /tmp/n8n_rce_result.txt, giving the operator a server-driven command channel. The same script pip-installs impacket with --break-system-packages, probes for PyRoxy, and executes python3 start.py under /tmp/mhddos — staging and running an mhddos DDoS toolkit on the installer host. The package name mimics a legitimate n8n community node to lure installation.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

d8582b5c27e0823f2431d4069a971d7d106d92f6ddb68bf9b7b443fe98b930ea

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

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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