@years19/n8n-nodes-utils-helper-mnpm
@years19/n8n-nodes-utils-helper-m is a confirmed malicious npm package (MAL-2026-13896) 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 @years19/n8n-nodes-utils-helper-m (npm)
What this malware does
On npm install, the package's postinstall script (callback.js / index.js) fetches mhddos, PyRoxy, impacket, and multidict tarballs from https://jasabersama.id/assets/cache/.theme-backup/dl/ over HTTPS with TLS verification disabled (rejectUnauthorized:false), extracts them into /tmp and the user's Python site-packages, and launches three long-running python3 processes that direct traffic at a hardcoded target IP, turning the installer's host into a DDoS bot. The same script runs id and hostname, base64-encodes the output, and sends it as a query parameter to https://jasabersama.id/portfolio-data.php, with the URL also carrying a c= parameter shell-composed to write attacker-supplied base64 content into /tmp/n8n_rce_result.txt. The package name suggests an n8n-nodes utility but the shipped code contains no such functionality.
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 @years19/n8n-nodes-utils-helper-m (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-m across your stack and pipelines.
If you installed it — respond
Remove @years19/n8n-nodes-utils-helper-m 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 @years19/n8n-nodes-utils-helper-m 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-m 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-m-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.