Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in ts-grok

Malware was discovered in the ts-grok npm package. Systems with the package installed or running should be considered fully compromised and require immediate remediation.

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

A malware incident was identified in the ts-grok npm package, published as GitHub Advisory GHSA-qp73-r9hh-6vq9 on June 25, 2026.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. The malware may have granted outside entities full control of affected systems.\n\nImmediate remediation is required, including rotation of all secrets and keys from a separate, uncompromised computer. 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\nThe affected package is ts-grok on npm.

Indicators of compromise

Packages
  • ts-grok

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the ts-grok package from all affected systems
  • Conduct a full security audit of any system that had ts-grok installed
  • Monitor affected systems for signs of persistent compromise or lateral movement
  • Review access logs and network traffic from systems that ran ts-grok
  • Consider full system reimaging if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-qp73-r9hh-6vq9 · GitHub Advisory Database

Cite this entry

"Malware in ts-grok." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 25, 2026. https://supplychainattack.org/incident/malware-in-ts-grok-jjsh0j

Suggest a correction

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

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package