Malware in autotel-sentry
Malware was discovered in the npm package autotel-sentry, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- autotel-sentry
The npm package autotel-sentry was found to contain malware. According to the GitHub Advisory (GHSA-rxgj-x3gg-2fg8), 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 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 a compromised npm package with potential for widespread impact across all systems where it was installed.
Indicators of compromise
- Packages
- autotel-sentry
Remediation
- Remove the autotel-sentry package immediately from all affected systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Conduct a full security audit of any system that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review package installation logs to identify all systems where autotel-sentry was deployed
Sources
- GitHub Advisory GHSA-rxgj-x3gg-2fg8 · GitHub Advisory Database
Cite this entry
"Malware in autotel-sentry." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-autotel-sentry-1pr8my
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 bcc-design-icons (npm)
bcc-design-icons@9999.0.0 on npm contains malicious postinstall script that exfiltrates hostname and package name to attacker-controlled IP 91.201.215.48:8000. The package lacks expected icon-library functionality and exhibits characteristics of a dependency-confusion attack targeting internal/private npm installers.
npmDependency confusionCompromised package - containedcritical
Malware in checkout-common-tokens
Malware was discovered in the npm package checkout-common-tokens. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - resolvedcritical
Malware in ulebkit
The npm package ulebkit contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in sui-move-graphql
Malware was discovered in the npm package sui-move-graphql. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
npmCompromised package