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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- autotel-playwright
A malware incident was identified in the npm package autotel-playwright, published as GitHub Advisory GHSA-6pcg-qh3x-h5pg on June 30, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system.\n\nWhile the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package alone will eliminate all malicious software resulting from the installation.\n\nAffected package: autotel-playwright (npm).
Indicators of compromise
- Packages
- autotel-playwright
Remediation
- Remove the autotel-playwright package immediately
- Rotate all secrets and keys stored on affected computers from a different, uncompromised system
- Perform a full security audit and malware scan of any system that had this package installed or running
- Review system logs for unauthorized access or activity
- Consider full system reimaging if compromise is suspected
Sources
- GitHub Advisory GHSA-6pcg-qh3x-h5pg · GitHub Advisory Database
Cite this entry
"Malware in autotel-playwright." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-autotel-playwright-uu0lcd
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 crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - resolvedcritical
Malicious code in ranux-dev (npm)
ranux-dev, an npm package, contained malicious code that substituted a popular WhatsApp library dependency with arbitrary code from an unaffiliated GitHub account. The package was heavily obfuscated and designed to harvest WhatsApp sessions and credentials from installers.
npmCompromised packageDependency confusion - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package