@years19/n8n-nodes-utils-helper-pnpm
@years19/n8n-nodes-utils-helper-p is a confirmed malicious npm package (MAL-2026-13899) 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-p (npm)
What this malware does
On npm install (postinstall) and on require of the main entry index.js, the package fetches multiple tarballs (mhddos, pyroxy-full, impacket, multidict) from jasabersama.id over an HTTPS connection with TLS verification disabled, extracts them to /tmp and the Python user site-packages directory, and launches three background python3 processes running mhddos against the hardcoded target 103.118.252.21 (UDP:80, TCP:443, GET:80 for 600 seconds). callback.js and index.js are byte-identical, so the payload fires both from the postinstall lifecycle and from require/import when n8n loads the community node, defeating --ignore-scripts. The script additionally collects id and hostname output plus attack-process status, base64-encodes them, and sends them via GET to https://jasabersama.id/portfolio-data.php with a k= key and a c= parameter that carries a shell command (echo <b64> | base64 -d >> /tmp/n8n_rce_result.txt), providing a reporting/command channel to the operator.
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-p (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-p across your stack and pipelines.
If you installed it — respond
Remove @years19/n8n-nodes-utils-helper-p 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-p 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-p 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-p-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.