Malware in @hoteldev/common
Malware was discovered in the npm package @hoteldev/common. Systems with this package installed or running are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with @hoteldev/common installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @hoteldev/common
A malicious package named @hoteldev/common was published to npm and distributed to users. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may have provided attackers with access to secrets, keys, and other sensitive data stored on affected systems.\n\nRemoval of the package does not guarantee removal of all malicious software, as the attacker may have established persistent access or deployed additional payloads during the compromise.\n\nAffected users must rotate all secrets and keys from a different, uncompromised computer and conduct a full security audit of their systems.
Indicators of compromise
- Packages
- @hoteldev/common
Remediation
- Immediately remove @hoteldev/common from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Conduct a full forensic analysis of affected systems for additional malware or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Notify any third parties or services that may have been affected by compromised credentials
Sources
- GitHub Advisory GHSA-62r9-p944-cjmg · GitHub Advisory Database
Cite this entry
"Malware in @hoteldev/common." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 6, 2026. https://supplychainattack.org/incident/malware-in-hoteldev-common-xa7uyq
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 autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting