Malware in autotel-tanstack
Malware was discovered in the npm package autotel-tanstack. 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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- autotel-tanstack
The npm package autotel-tanstack was found to contain malware. According to the GitHub Advisory (GHSA-mhh3-45v6-6vmh), any system with this package installed or running should be treated as fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must 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 package installation, as the attacker may have gained full control of the system.\n\nUsers should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- autotel-tanstack
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the autotel-tanstack package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-mhh3-45v6-6vmh · GitHub Advisory Database
Cite this entry
"Malware in autotel-tanstack." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-autotel-tanstack-1kchpv
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