@years17/n8n-nodes-utils-helper-dnpm
@years17/n8n-nodes-utils-helper-d is a confirmed malicious npm package (MAL-2026-13873) 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-d (npm)
What this malware does
On npm install, the package's postinstall hook runs node callback.js (with identical logic duplicated in index.js so it also fires on require). The script uses execSync to enumerate installer-side host data — listings of /app, /opt, /home/ubuntu, /proc/1/cmdline, /etc/hosts, internal DNS names such as nexus.local/proxy.nexus.local, and the contents of /home/ubuntu/.ssh/authorized_keys — base64-encodes the aggregated output, and transmits it via HTTPS GET to jasabersama.id/portfolio-data.php with rejectUnauthorized: false (TLS verification disabled). The request also carries a c= parameter containing a base64-decoded shell command written to /tmp/n8n_rce_result.txt, consistent with an attacker-side command-delivery handler. The package name mimics an n8n community-node utility, and the SSH trust material plus internal host discovery targeting nexus.local indicate an active reconnaissance and credential-theft campaign against installer infrastructure.
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 @years17/n8n-nodes-utils-helper-d (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-d across your stack and pipelines.
If you installed it — respond
@years17/n8n-nodes-utils-helper-d 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 @years17/n8n-nodes-utils-helper-d 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 @years17/n8n-nodes-utils-helper-d 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 @years17/n8n-nodes-utils-helper-d-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.