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

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

Advisory published Updated

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

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

What this malware does

The package's postinstall script (callback.js) and its declared main entry (index.js, byte-identical to callback.js) fetch a tarball and a get-pip installer from https://jasabersama.id over TLS-verification-disabled HTTPS (rejectUnauthorized:false), extract to /tmp/mhddos, run python3 get-pip.py --break-system-packages, and execute python3 /tmp/mhddos/start.py — the fetched project is the MHDDoS/PyRoxy denial-of-service tool. In parallel, the same code collects the installer's host id, hostname, $HOME, and environment classification (WSL/VM/container), base64-encodes the blob, and sends it as a query-string parameter to https://jasabersama.id/portfolio-data.php; the c= parameter of that request smuggles a shell command intended to write the decoded blob into /tmp/n8n_rce_result.txt on the receiving server. Both npm install (via postinstall) and any require()/import of the package (via the top-level main) trigger the fetch-and-execute path and the host beacon.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

b16d7ce451e7cdf1d3486a22c2ec25e3f56651ce45e132178839e2283918183f

Detection & response playbook

Backdoor / remote access

  1. Find it

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

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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