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 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