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

Advisory published Updated

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

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

What this malware does

On npm install, the declared postinstall script node callback.js performs two hostile actions against the installer. First, it downloads a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/mhddos.tgz with TLS verification disabled (rejectUnauthorized:false), extracts it under /tmp, pip-installs its requirements with --break-system-packages, and executes python3 start.py — the archive name and structure correspond to the MHDDoS attack tool. Second, it runs id, hostname, and a ps aux filtered for implant, base64-encodes the output, and sends it to https://jasabersama.id/portfolio-data.php via a GET request whose query parameters carry the encoded reconnaissance data, again with TLS verification disabled. Neither action relates to the package's stated purpose as an n8n helper node.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

55fa2e2abba500f0c2863993fb8d51c3363f22a3fa8917fdf73e4b2545b81ea6

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove @years18/n8n-nodes-utils-helper-c 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-c 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-c 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-017403

References

Credits

  • Amazon Inspector · finder

Detect & block this

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