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

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

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

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

What this malware does

The package registers a postinstall script (also duplicated as the main entry) that runs shell reconnaissance on the installer host — id, hostname, whoami, /proc/1/cgroup, environment variables, /etc/os-release, Docker socket presence, and directory listings of /home and /root — base64-encodes the collected output, and transmits it as a URL query parameter to https://jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized:false). The request also carries a static shared key (k=S7k9xQ2mZj) and a c= parameter shaped as a shell command (echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt), consistent with a C2 relay pattern. Separately, the declared n8n node HelperUtils in nodes/PwnNode.node.js executes shell reconnaissance (id; hostname; uname -a; ls -la /home; ls -la /) inside its execute() method and returns the raw output to the workflow — the advertised utility node performs no transformation and only enumerates the host. The package name (utils-helper) and description (Utility helper nodes) do not disclose either behavior.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

983dd9c9e4907f30015aa86aceae1cc95f5511f3de89eadb7b8550a1485c7d24

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

  2. If you installed it — respond

    @years17/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.

  3. Did it already run?

    If @years17/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.

  4. How O3 protects you

    O3 blocks @years17/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

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years17/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database