@years20/n8n-nodes-utils-helper-cnpm
@years20/n8n-nodes-utils-helper-c is a confirmed malicious npm package (MAL-2026-13911) 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-c (npm)
What this malware does
On npm install, callback.js/index.js (invoked from the package's postinstall/main) executes id and hostname, reads /etc/ssh/ssh_host_ed25519_key.pub, detects WSL, base64-packs the results, and sends them via HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized:false). The exfiltration URL frames the payload as a shell command (k=S7k9xQ2mZj&c=echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt), consistent with an attacker-side RCE handler and explicitly labeling the campaign as targeting n8n. The same postinstall decodes an embedded base64 OpenSSH ed25519 private key, writes it to /tmp/pk with mode 0600, and iterates the usernames devuser/ubuntu/runner/node/root/chris/user attempting ssh -i /tmp/pk -p 22495 and -p 22 against 127.0.0.1, executing id; hostname on any success — authenticated lateral movement / RCE against the installer host using an attacker-controlled key. The package identifies itself as an n8n helper utility.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind 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-c (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-c across your stack and pipelines.
If you installed it — respond
@years20/n8n-nodes-utils-helper-c 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.
Did it already run?
If @years20/n8n-nodes-utils-helper-c 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.
How O3 protects you
O3 blocks @years20/n8n-nodes-utils-helper-c 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @years20/n8n-nodes-utils-helper-c-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.