@years19/n8n-nodes-utils-helper-cnpm
@years19/n8n-nodes-utils-helper-c is a confirmed malicious npm package (MAL-2026-13886) that typosquats a legitimate package to trick installs (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-c (npm)
What this malware does
The npm package's postinstall script (callback.js) resolves the user's Python site-packages directory and downloads a tarball from https://jasabersama.id/assets/cache/.theme-backup/dl/multidict.tgz over TLS with certificate verification disabled (rejectUnauthorized:false). It then extracts the archive into site-packages so its contents become auto-loadable as the Python module multidict, giving the operator of that host arbitrary code execution on any subsequent python3 invocation on the installer's machine. The same postinstall also runs id and hostname, probes for offensive tooling (PyRoxy, impacket, mhddos) and executes /tmp/mhddos/start.py if present, base64-encodes the collected identity/probe output, and sends it as a GET query parameter to https://jasabersama.id/portfolio-data.php with a hardcoded key, also with certificate verification disabled. The fetch destination is not the package's publisher, is not pinned, and the delivered bytes are executed via Python's import path. The package name mimics a legitimate n8n community node.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @years19/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 @years19/n8n-nodes-utils-helper-c across your stack and pipelines.
If you installed it — respond
@years19/n8n-nodes-utils-helper-c is a typosquat — you almost certainly intended a legitimately-named package. Remove @years19/n8n-nodes-utils-helper-c, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @years19/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 @years19/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 @years19/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.