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

@years20/n8n-nodes-utils-helper-fnpm

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

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

What this malware does

The package auto-executes a reconnaissance and exfiltration payload both at install (via scripts.postinstall running callback.js) and on require (identical top-level code in index.js). The payload collects host identity (id, hostname, network interfaces, WSL detection), reads the SSH host public key from /etc/ssh/ssh_host_ed25519_key.pub, and probes internal-network ports including 10.131.106.231:22495. The aggregated data is base64-encoded and sent via https.get to https://jasabersama.id/portfolio-data.php with TLS certificate verification disabled (rejectUnauthorized:false). The package name suggests it is masquerading as an n8n helper node, but the shipped code has no n8n functionality — only the recon/exfil payload.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

c8297c0d5a6f2c446285924983ee24b195c180fbaa75a7826e8e925497eddab7

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @years20/n8n-nodes-utils-helper-f (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 @years20/n8n-nodes-utils-helper-f across your stack and pipelines.

  2. If you installed it — respond

    @years20/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 @years20/n8n-nodes-utils-helper-f 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 @years20/n8n-nodes-utils-helper-f 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. @years20/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-017596

References

Credits

  • Amazon Inspector · finder

Detect & block this

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