Malware in autotel-backends
Malware was discovered in the npm package autotel-backends. 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
- autotel-backends
A critical malware incident was identified in the npm package autotel-backends. According to the GitHub Advisory (GHSA-9p9m-f2hg-9gxm), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the malicious 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\nThis represents a critical supply chain attack through package compromise, affecting all users of the autotel-backends npm package.
Indicators of compromise
- Packages
- autotel-backends
Remediation
- Immediately isolate any system with autotel-backends installed from the network
- Rotate all secrets, API keys, and credentials from a clean, uncompromised system
- Remove the autotel-backends package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
Sources
- GitHub Advisory GHSA-9p9m-f2hg-9gxm · GitHub Advisory Database
Cite this entry
"Malware in autotel-backends." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-autotel-backends-1pcaac
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 ladash-cli (npm)
ladash-cli is a typosquat package on npm that executes malicious code during installation. The postinstall script downloads and executes a Windows binary, with special handling for WSL environments to compromise the underlying Windows host.
npmTyposquattingCompromised package - containedcritical
Malicious code in comand (npm)
The npm package 'comand' contained malicious code that executed automatically on install via postinstall.js, exfiltrating platform information and downloading an unsigned executable (main.exe) to Windows systems or via WSL PowerShell bridges. The package name appears to be a typosquat of 'command', and the GitHub owner (braz1) does not match the npm publisher.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in core-js-gns (npm)
The npm package core-js-gns contained malicious code in its postinstall hook that exfiltrated system information and executed remotely-fetched Python code on developer machines. The package name was a typosquat of the legitimate core-js library.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in comander-lib (npm)
comander-lib@1.0.0 is a typosquat of the legitimate `commander` package containing malicious code. The package's postinstall script exfiltrates system information to a C2 server and downloads and executes a Windows payload, with capability to escape WSL/Linux sandboxes via PowerShell.
npmTyposquattingCompromised package