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-fnpm

Advisory published Updated

@years18/n8n-nodes-utils-helper-f is a confirmed malicious npm package (MAL-2026-13852) that steals credentials and exfiltrates sensitive data (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-f (npm)

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

What this malware does

On npm install, the package's postinstall hook (callback.js / index.js) executes shell commands including id and hostname, probes the internal RFC1918 address 10.131.106.93:8888 via /dev/tcp, base64-encodes the collected output, and sends it via HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). The server-side query is constructed to base64-decode the payload into /tmp/n8n_rce_result.txt. The same postinstall path invokes python3 /tmp/get-pip.py --break-system-packages, pip install -r /tmp/mhddos/requirements.txt, and python3 start.py from /tmp/mhddos, staging and running the mhddos DDoS framework on the installer's machine at install time. The combination yields host reconnaissance exfiltration, internal-network probing, and install-time remote code execution turning the installer into a DDoS node.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

df58050e02ff53c728a303196575150af9e64959761f10079284077b1c274572

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @years18/n8n-nodes-utils-helper-f is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years18/n8n-nodes-utils-helper-f-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

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