Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in ts-ecro

Malware was discovered in the npm package ts-ecro, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with ts-ecro installed or running
Ecosystems
Attack vectors
Affected entities
  • ts-ecro

A critical malware incident was identified in the npm package ts-ecro. According to the GitHub Advisory (GHSA-cwjv-7gg4-fp86), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package grants outside entities full control of affected systems. All secrets and keys stored on compromised computers must be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, the advisory notes that full system compromise may mean removing the package alone will not eliminate all malicious software that may have been installed as a result of the initial compromise.

Indicators of compromise

Packages
  • ts-ecro

Remediation

  • Immediately remove the ts-ecro package from all systems
  • Rotate all secrets, API keys, and credentials from a different, unaffected computer
  • Perform a full security audit and malware scan of any system that had ts-ecro installed
  • Review system logs and access logs for any unauthorized activity during the period the package was installed
  • Consider full system reimaging if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-cwjv-7gg4-fp86 · GitHub Advisory Database

Cite this entry

"Malware in ts-ecro." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 19, 2026; last updated June 20, 2026. https://supplychainattack.org/incident/malware-in-ts-ecro-1r2ewb

Suggest a correction

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

  1. resolvedcritical

    Malicious code in elephant-tusk-runner (npm)

    The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.

    npmCompromised package
  2. resolvedcritical

    Malicious code in santana-baileys (npm)

    Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.

    npmCompromised package
  3. containedcritical

    Malicious code in cewe-npm-cops (npm)

    cewe-npm-cops@99.9.9 is a malicious npm package that exfiltrates the installer's machine hostname via DNS to an attacker-controlled out-of-band service. The package uses a high version number (99.9.9) to override internal packages during dependency resolution and executes a preinstall script that leaks system information.

    npmCompromised packageDependency confusion
  4. resolvedcritical

    Malicious code in dpdgroup-css (npm)

    The npm package dpdgroup-css contained malicious code that executed on installation, exfiltrating the installer's hostname to an external IP address. The package name mimics an internal DPDgroup scope, suggesting a dependency-confusion attack targeting the courier organization.

    npmCompromised packageDependency confusion