Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

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

The npm package @years19/n8n-nodes-utils-helper-h contained malicious code that executed on install, downloading DDoS tools, launching attacks against a hardcoded target, and exfiltrating host information to an attacker-controlled server.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any npm user who installed @years19/n8n-nodes-utils-helper-h
Ecosystems
Attack vectors
Affected entities
  • @years19/n8n-nodes-utils-helper-hMalicious npm package

The npm package @years19/n8n-nodes-utils-helper-h was published with malicious code embedded in a postinstall hook (callback.js/index.js). Upon installation, the script downloaded four Python tarballs (mhddos, PyRoxy, impacket, and related payloads) from https://jasabersama.id/assets/cache/.theme-backup/dl/ with TLS certificate validation disabled, extracted them into /tmp and the user's Python site-packages, and executed python3 start.py in the background.\n\nThe malicious code launched three concurrent 600-second DDoS floods (UDP, TCP, and GET requests) against the hardcoded target 103.118.252.21 on ports 80/443 from the installer's host. It then collected host identity information (id, hostname), dependency-check output, process counts, and attack logs, base64-encoded them, and sent them as query parameters to https://jasabersama.id/portfolio-data.php with a hardcoded key. Both the payload downloads and the beacon communication disabled TLS verification (rejectUnauthorized:false).\n\nThe incident was identified and credited to the OpenSSF malicious-packages repository (MAL-2026-13891).

Indicators of compromise

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

Remediation

  • Immediately uninstall @years19/n8n-nodes-utils-helper-h from all systems
  • Audit npm install logs to identify when the package was installed
  • Check for unexpected Python processes or DDoS tools in /tmp and Python site-packages directories
  • Monitor outbound connections to jasabersama.id for data exfiltration
  • Review firewall logs for DDoS traffic originating from affected hosts targeting 103.118.252.21
  • Regenerate any credentials or sensitive data that may have been exposed via the host identity collection
  • Use npm audit to identify and remove any other malicious packages from the dependency tree

Sources

  1. GitHub Advisory GHSA-vxwh-8hm6-wcpp · GitHub Advisory Database

Cite this entry

"Malicious code in @years19/n8n-nodes-utils-helper-h (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-h-npm-4xhxvx

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