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

@years20/n8n-nodes-utils-helper-gnpm

Advisory published Updated

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

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

What this malware does

On npm install, the package's postinstall script (duplicated in the main module) executes shell commands to collect host identity (id, hostname, pwd), locates n8n installation directories, enumerates running n8n processes, and reads n8n-related environment variables. The collected output is base64-encoded and sent via HTTPS GET to the hardcoded endpoint https://jasabersama.id/portfolio-data.php with TLS certificate validation disabled (rejectUnauthorized: false). The request includes a static key parameter k=S7k9xQ2mZj and a c= parameter containing a shell command payload (echo <base64> | base64 -d >> /tmp/n8n_rce_result.txt), and the endpoint filename plus payload shape indicate an RCE staging harness. The package's advertised utility helper purpose is a cover; the only substantive content is the install-time recon and beacon.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

55ed8dc4c0467877e129dc4b2035e154dc4fec24bfda412d649fa02ed7150133

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @years20/n8n-nodes-utils-helper-g 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 @years20/n8n-nodes-utils-helper-g 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. @years20/n8n-nodes-utils-helper-g 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-017613

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @years20/n8n-nodes-utils-helper-g-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
@years20/n8n-nodes-utils-helper-g (npm) malicious package — MAL-2026-13916 | O3 Security