Malware in autotel-cli
The npm package autotel-cli was found to contain malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with autotel-cli installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- autotel-clinpm package containing malware
The npm package autotel-cli was identified as containing malware. According to the GitHub Advisory (GHSA-3729-344x-9v28), any computer that has 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, 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 initial compromise, given that the attacker may have gained full control of the system.\n\nUsers should treat any system that has executed this package as potentially containing persistent malware and take appropriate incident response measures.
Indicators of compromise
- Packages
- autotel-cli
Remediation
- Immediately remove the autotel-cli package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and perform forensic analysis or rebuild affected systems
- Monitor for any unauthorized access or activity on systems that had autotel-cli installed
- Check npm audit logs and package.json files to identify all systems where autotel-cli was installed
Sources
- GitHub Advisory GHSA-3729-344x-9v28 · GitHub Advisory Database
Cite this entry
"Malware in autotel-cli." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-autotel-cli-1a9rig
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package