Malware in awesome-ts-jest
Malware was discovered in the npm package awesome-ts-jest. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- awesome-ts-jest
The npm package awesome-ts-jest was found to contain malware. According to the GitHub Security Advisory (GHSA-7xr4-v32m-4h8x), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: 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\nThe advisory recommends treating any system that has run this package as potentially under full external control and taking appropriate security measures accordingly.
Indicators of compromise
- Packages
- awesome-ts-jest
Remediation
- Immediately remove the awesome-ts-jest package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Perform a full security audit and malware scan on any system that had this package installed or running
- Review system logs and network activity for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially compromised and take appropriate incident response measures
- Update any systems that may have been affected to use a safe alternative or wait for a patched version
Sources
- GitHub Advisory GHSA-7xr4-v32m-4h8x · GitHub Advisory Database
Cite this entry
"Malware in awesome-ts-jest." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-awesome-ts-jest-1bf0n4
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - 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 - 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 - 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