Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in @years19/n8n-nodes-utils-helper-k (npm)

The npm package @years19/n8n-nodes-utils-helper-k contains malicious code that downloads and executes DDoS tooling on install and import, while exfiltrating host identity to an attacker-controlled server. The package has no legitimate functionality and is purely a DDoS botnet dropper.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any user installing @years19/n8n-nodes-utils-helper-k or importing it as an n8n community node; systems become DDoS botnet nodes and leak host identity to attacker C2.
Ecosystems
Attack vectors
Affected entities
  • @years19/n8n-nodes-utils-helper-kMalicious npm package masquerading as n8n utility helper

The package @years19/n8n-nodes-utils-helper-k was published to npm as a fake n8n utility helper but contains only malicious code. Its postinstall script (callback.js) and main entry point (index.js, a byte-for-byte duplicate) execute an identical malicious chain without user interaction.

The malicious behavior includes: downloading multiple DDoS toolkits (mhddos, PyRoxy, impacket, multidict) from https://jasabersama.id/assets/cache/.theme-backup/dl/ with TLS verification disabled, unpacking them into /tmp and Python site-packages, and executing python3 start.py to launch UDP/TCP/GET flood attacks against 103.118.252.21. The package also collects the installer's id and hostname output, base64-encodes it, and sends it as a GET parameter to https://jasabersama.id/portfolio-data.php (also with TLS verification disabled) to beacon the victim's identity to the attacker's C2.

The postinstall hook fires automatically on npm install, and the identical main entry re-executes the chain on any require or import, including when n8n loads this as a community node. This ensures persistence and repeated execution across multiple trigger points.

The package presents no legitimate n8n utility functionality; its sole purpose is to compromise the host system into a DDoS botnet while exfiltrating identifying information to the attacker.

Indicators of compromise

Packages
  • @years19/n8n-nodes-utils-helper-k
Domains
  • jasabersama.id
IPs
  • 103.118.252.21

Remediation

  • Immediately uninstall @years19/n8n-nodes-utils-helper-k from all systems: npm uninstall @years19/n8n-nodes-utils-helper-k
  • Audit npm install logs and package-lock.json to identify all systems where this package was installed
  • Inspect /tmp and Python site-packages directories for dropped DDoS toolkits (mhddos, PyRoxy, impacket, multidict) and remove them
  • Monitor network traffic for outbound UDP/TCP/GET flood attacks to 103.118.252.21 and block at firewall
  • Review firewall and network logs for any connections to jasabersama.id
  • Regenerate SSH keys and credentials on affected systems, as host identity has been exfiltrated
  • Update npm to the latest version and run npm audit to detect other malicious packages
  • Consider blocking the attacker's C2 domain (jasabersama.id) and IP (103.118.252.21) at the network perimeter

Sources

  1. GitHub Advisory GHSA-v9r5-92f6-v927 · GitHub Advisory Database

Cite this entry

"Malicious code in @years19/n8n-nodes-utils-helper-k (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 12, 2026; last updated August 12, 2026. https://supplychainattack.org/incident/malicious-code-in-years19-n8n-nodes-utils-helper-k-npm-1jhe04

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malware in svelte-dim-kit

    The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.

    npmCompromised package
  2. containedcritical

    Malicious code in @syncraft-labs/react (npm)

    The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.

    npmCompromised package
  3. containedcritical

    Malicious code in stillm4ddpocs-demo-sprocket (npm)

    The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.

    npmCompromised packageDependency confusion
  4. resolvedcritical

    Malicious code in stillm4ddpocs-rtest-bravo (npm)

    The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.

    npmCompromised package