Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in ts-numbering

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

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

The npm package ts-numbering has been identified as containing malware. According to the GitHub advisory (GHSA-fvpj-9j2j-grmr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated 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 compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.

Indicators of compromise

Packages
  • ts-numbering

Remediation

  • Immediately isolate any system with ts-numbering installed from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the ts-numbering package from all affected systems
  • Conduct a full security audit and malware scan of affected systems
  • Review system logs for any suspicious activity or unauthorized access
  • Consider full system reimaging if compromise is confirmed
  • Notify all users and systems that may have been affected by the compromise

Sources

  1. GitHub Advisory GHSA-fvpj-9j2j-grmr · GitHub Advisory Database

Cite this entry

"Malware in ts-numbering." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-ts-numbering-15r5tc

Suggest a correction

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

  1. containedcritical

    Malware in crud-respect

    The npm package crud-respect was found to contain malware. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer.

    npmCompromised package
  2. activecritical

    Malware in chai-as-attested

    The npm package chai-as-attested contains malware that provides full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys should be rotated immediately from a different machine.

    npmCompromised package
  3. resolvedcritical

    Malware in eslint-helper-1

    Malware was discovered in the npm package eslint-helper-1, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  4. activecritical

    Malware in onboarding-respects-modal

    Malware discovered in the npm package onboarding-respects-modal. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package