@years18/n8n-nodes-utils-helper-cnpm
@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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @years18/n8n-nodes-utils-helper-c (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @years18/n8n-nodes-utils-helper-c across your stack and pipelines.
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.
Did it already run?
If @years18/n8n-nodes-utils-helper-c was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @years18/n8n-nodes-utils-helper-c before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
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.