Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in ts-linting-builder

The npm package ts-linting-builder contained malware that could fully compromise affected systems. All systems with this package installed should be considered compromised and all secrets and keys rotated from a different computer.

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

The npm package ts-linting-builder was found to contain malware. According to the GitHub Advisory (GHSA-8mpj-272v-jhv7), 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, unaffected computer. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting the npm ecosystem.

Indicators of compromise

Packages
  • ts-linting-builder

Remediation

  • Remove the ts-linting-builder package immediately
  • Rotate all secrets, API keys, and credentials from a different, unaffected computer
  • Audit system logs for unauthorized access or activity
  • Consider the affected system fully compromised and plan for complete remediation or replacement
  • Check for and remove any additional malicious software that may have been installed

Sources

  1. GitHub Advisory GHSA-8mpj-272v-jhv7 · GitHub Advisory Database

Cite this entry

"Malware in ts-linting-builder." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-ts-linting-builder-1vd1q9

Suggest a correction

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

  1. containedcritical

    Malware in awaitly-libsql

    The npm package awaitly-libsql was found to contain malware. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

    npmCompromised package
  2. containedcritical

    Malware in autotel-mcp-instrumentation

    Malware was discovered in the npm package autotel-mcp-instrumentation. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  3. activecritical

    Malware in autotel-pact

    The npm package autotel-pact contains malware that grants full control of affected systems to an outside entity. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  4. containedcritical

    Malware in autotel-playwright

    Malware was discovered in the npm package autotel-playwright. Systems with this package installed or running are considered fully compromised and require immediate remediation.

    npmCompromised package