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

@years19/n8n-nodes-utils-helper-tnpm

Advisory published Updated

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

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

What this malware does

The package's postinstall script (callback.js) and its main entry point (index.js, byte-identical) execute automatically on npm install and on require()/import. They write a Python UDP/TCP flood script to /tmp/attack.py and launch it via nohup python3 /tmp/attack.py... & targeting the hardcoded IP 103.118.252.21 for 600 seconds, turning the installer host into a DDoS participant. In parallel, they collect the output of id and hostname along with process and loadavg data, base64-encode it, and send it via https.get to https://jasabersama.id/portfolio-data.php with TLS certificate verification disabled (rejectUnauthorized: false). The package is presented as an n8n utility node, but its actual behavior is remote code execution against a third-party target combined with installer host-identity exfiltration.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

69298edbeb56ed182ba1b98c575c24b9ac53138a0a2cadfd9fd3dbbf3e637546

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-t 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 @years19/n8n-nodes-utils-helper-t 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. @years19/n8n-nodes-utils-helper-t 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-017585

References

Credits

  • Amazon Inspector · finder

Detect & block this

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