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-enpm

Advisory published Updated

@years17/n8n-nodes-utils-helper-e is a confirmed malicious npm package (MAL-2026-13874) that opens a backdoor for remote access (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-e (npm)

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

What this malware does

On install, this package auto-executes callback.js via a postinstall hook (identical to index.js). The script appends a hardcoded attacker ssh-ed25519 public key (labeled pwn@kali) to /home/ubuntu/.ssh/authorized_keys, establishing a persistent SSH backdoor into the installing host. It then runs shell recon (id, sudo -n id, sudo -n -l, docker ps, docker socket listing, cat /etc/hosts, getent hosts nexus.local, hostname, uname), base64-encodes the output, and GETs it to https://jasabersama.id/portfolio-data.php with TLS validation disabled (rejectUnauthorized: false). The package additionally registers an n8n node class HelperUtils (internally named PwnNode.node.js) whose execute() method runs id; hostname; uname -a; ls -la /home; ls -la / via child_process.execSync and returns the output with a pwned: true marker.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

af9f56bdea8e3bb900e25683a669d233760c33c4b028dd03ede76a2114682096

Detection & response playbook

Backdoor / remote access
  1. Find it

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

  2. If you installed it — respond

    @years17/n8n-nodes-utils-helper-e establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If @years17/n8n-nodes-utils-helper-e 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-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-017551

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years17/n8n-nodes-utils-helper-e-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

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