NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @years18 published 23 malicious packages. See the full campaign →
Malicious package

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

Advisory published Updated

@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)

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

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

be4bb7a1bd57477bf3cbbb1ccc9b76a2ed8b96a8117e0a4cad882b76404c86fb

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @years18/n8n-nodes-utils-helper-r (version 1.0.0).

  2. 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.

  3. Did it already run?

    If @years18/n8n-nodes-utils-helper-r was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @years18/n8n-nodes-utils-helper-r 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-017396

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.

Malware detection Runtime egress monitoring

Explore

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