@years18/n8n-nodes-utils-helper-ynpm
@years18/n8n-nodes-utils-helper-y is a confirmed malicious npm package (MAL-2026-13883) 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-y (npm)
What this malware does
The package's postinstall hook (node callback.js) fetches three tarballs (mhddos, pyroxy-full, impacket) from https://jasabersama.id/assets/cache/.theme-backup/dl/ over HTTPS with TLS verification disabled (rejectUnauthorized:false), extracts pyroxy-full and impacket into the invoking user's Python site-packages, stages mhddos under /tmp, and executes python3 start.py from the extracted mhddos toolkit. Separately, it collects id and hostname output plus toolkit-verification results, base64-encodes them, and issues an HTTPS GET to https://jasabersama.id/portfolio-data.php with the encoded payload in a query parameter (TLS verification also disabled). Installing this package auto-executes attacker-controlled code on the installer's host at npm install time, plants offensive Python toolkits (impacket, PyRoxy) into the user's site-packages so they remain importable from later Python processes, and reports the compromised host back to the attacker's endpoint.
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-y (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-y across your stack and pipelines.
If you installed it — respond
Remove @years18/n8n-nodes-utils-helper-y 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-y 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-y 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-y-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.