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

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

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

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

What this malware does

The package presents as an n8n community-nodes helper but ships a malicious postinstall script (callback.js) and a byte-identical main entrypoint (index.js) that fire on npm install and on module load. The script runs id, hostname, and WSL detection, reads the host SSH public key fingerprint from /etc/ssh/ssh_host_ed25519_key.pub, base64-encodes the collected data, and sends it via HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized: false). It also decodes a bundled OpenSSH ed25519 private key to /tmp/pk (chmod 600) and iterates ssh -i /tmp/pk login attempts against 127.0.0.1/localhost on ports 22495 and 22 as devuser/ubuntu/runner/node/root/chris/user, executing id; hostname on any account that accepts the key. The C2 URL path /portfolio-data.php?k=S7k9xQ2mZj&c=<url-encoded shell command> is shaped as a command channel, indicating the endpoint is dual-use exfiltration and remote-execution infrastructure.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

89d61386ef6d8694ecf5f0578b5fe77156f475f76a8e97a1b2e834821cfbe0df

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

  2. If you installed it — respond

    @years20/n8n-nodes-utils-helper-e 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-e 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-e 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-e 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-017581

References

Credits

  • Amazon Inspector · finder

Detect & block this

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