NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: @years17 published 10 malicious packages. See the full campaign →
Malicious package

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

Advisory published Updated

@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)

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

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

cae13b1ae51e25930b719e8953b7349777e5b6c98c514490a937eab4136de603

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @years17/n8n-nodes-utils-helper-d (version 1.0.0).

  2. 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.

  3. Did it already run?

    If @years17/n8n-nodes-utils-helper-d was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @years17/n8n-nodes-utils-helper-d 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-017556

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.

Explore

@years17/n8n-nodes-utils-helper-d (npm) malicious package — MAL-2026-13873 | O3 Security