Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in ts-big-ecro

The npm package ts-big-ecro contained malware that fully compromised any system where it was installed. All secrets and keys on affected systems should be rotated immediately, and the package should be removed.

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

The npm package ts-big-ecro was found to contain malware. According to the GitHub Advisory (GHSA-3cg2-mrw5-67r6), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.

Indicators of compromise

Packages
  • ts-big-ecro

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the ts-big-ecro package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had ts-big-ecro installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Consider rebuilding affected systems from clean media if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-3cg2-mrw5-67r6 · GitHub Advisory Database

Cite this entry

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

Suggest a correction

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

  1. activecritical

    Malware in internallib_v688

    Malware discovered in the npm package internallib_v688. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malicious code in @zzzgenesis00/bip39-generator (npm)

    The npm package @zzzgenesis00/bip39-generator version 3.1.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.

    npmCompromised package
  3. containedcritical

    Malware in accounts-final-form

    The npm package accounts-final-form contained malware, potentially giving outside entities full control of affected systems. All systems with this package installed should be considered fully compromised.

    npmCompromised package
  4. containedcritical

    Malicious code in simple-date-formatter-new-1 (npm)

    The npm package simple-date-formatter-new-1 version 1.0.0 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with domains associated with malicious activity and executes commands associated with malicious behavior.

    npmCompromised package