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

@years17/n8n-nodes-utils-helper-hnpm

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

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

What this malware does

The package's postinstall script executes callback.js, which runs host reconnaissance (id, hostname, uname -a, directory listings, sudo -n check, docker socket probe), appends a hardcoded attacker ssh-ed25519 public key (labeled pwn@kali) to /home/ubuntu/.ssh/authorized_keys establishing persistent SSH access, and exfiltrates base64-encoded recon output via HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized:false). Additionally, the bundled n8n node (PwnNode.node.js) exposes a HelperUtils.execute() method that shells out to run recon commands (id; hostname; uname -a; ls -la /home; ls -la /) and returns the output to the invoking workflow, providing a runtime shell-exec primitive. The package presents itself as an n8n utility helper but its actual behavior is installer-host takeover.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

aba5b7d9e03a0f3796945ee4c55a6f32169b8f32b794dad9c1b450883667116b

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 @years17/n8n-nodes-utils-helper-h (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 @years17/n8n-nodes-utils-helper-h across your stack and pipelines.

  2. If you installed it — respond

    @years17/n8n-nodes-utils-helper-h 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 @years17/n8n-nodes-utils-helper-h 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 @years17/n8n-nodes-utils-helper-h 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. @years17/n8n-nodes-utils-helper-h 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-017554

References

Credits

  • Amazon Inspector · finder

Detect & block this

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