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

Advisory published Updated

@years18/n8n-nodes-utils-helper-x is a confirmed malicious npm package (MAL-2026-13868) that executes malicious code on install (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-x (npm)

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

What this malware does

Package presents itself as an n8n utility helper but ships a 213-byte stub node and a hostile postinstall (node callback.js). On npm install, callback.js fetches two tarballs (impacket.tgz, pyroxy.tgz) over HTTPS with TLS verification disabled from jasabersama.id/assets/cache/.theme-backup/dl/, extracts them into the installer's Python user site-packages so any subsequent Python import runs attacker-controlled code, and probes /tmp/mhddos/start.py (MHDDoS DDoS tooling). The same script collects id and hostname command output plus install-step status, base64-encodes the buffer, and sends it via HTTPS GET to https://jasabersama.id/portfolio-data.php as a URL parameter, indexing compromised hosts. The declared package purpose does not match the shipped behavior; the host is publisher-mismatched and TLS verification is disabled.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

6db9e566808d6a2ce38311e17939cd39ba94fc191cf5c44ab7b08b369840ba08

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove @years18/n8n-nodes-utils-helper-x from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

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