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

Advisory published Updated

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

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

What this malware does

The package's postinstall hook runs node callback.js, and package.json declares main=index.js which is byte-identical to callback.js, so both npm install and require() of the package execute the same payload. The payload writes /tmp/attack2.py — a threaded UDP/TCP flood loop targeting 103.118.252.21 for 900 seconds — and launches it via nohup python3 /tmp/attack2.py &, weaponizing the installer's host and IP as a DDoS bot. In parallel, it collects the output of id, hostname, a process check and /proc/loadavg, base64-encodes it, and sends it over HTTPS GET to jasabersama.id/portfolio-data.php with TLS verification disabled (rejectUnauthorized:false). The package is presented as an n8n utility helper but ships no such functionality; its only observable behavior is the DDoS launcher and host-identity beacon.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

da3601885350a7fc85f418da9fb3f800a5e76949562ad23ac44d5c2b068088c4

Detection & response playbook

Backdoor / remote access

  1. Find it

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

  2. If you installed it — respond

    @years19/n8n-nodes-utils-helper-x 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 @years19/n8n-nodes-utils-helper-x 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-x 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-017580

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@years19/n8n-nodes-utils-helper-x (npm) malicious package — MAL-2026-13907 | O3 Security