Malware in awaitly-mongo
The npm package awaitly-mongo was found to contain malware, resulting in full system compromise for any computer with the package installed or running. The advisory recommends treating affected systems as fully compromised and rotating all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with awaitly-mongo installed or running
- Ecosystems
- Attack vectors
- Affected entities
- awaitly-mongonpm package
The npm package awaitly-mongo was identified as containing malware. According to the GitHub Security Advisory (GHSA-4vpc-g7mx-4m5v), 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 immediately from a different, unaffected computer. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package will remove all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across development and production environments.
Indicators of compromise
- Packages
- awaitly-mongo
Remediation
- Immediately remove the awaitly-mongo package from all affected systems
- Rotate all secrets, API keys, credentials, and signing keys from a different, unaffected computer
- Assume full system compromise and conduct a thorough security audit of affected machines
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider rebuilding affected systems from clean media if possible
- Notify all users and stakeholders who may have been affected by systems running this package
Sources
- GitHub Advisory GHSA-4vpc-g7mx-4m5v · GitHub Advisory Database
Cite this entry
"Malware in awaitly-mongo." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-awaitly-mongo-190ak5
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in autotel-playwright
Malware was discovered in the npm package autotel-playwright. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in awaitly-libsql
The npm package awaitly-libsql was found to contain malware. 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.
npmCompromised package - activecritical
Malware in autotel-drizzle
Malware discovered in the npm package autotel-drizzle. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in autotel-pact
The npm package autotel-pact contains malware that grants full control of affected systems to an outside entity. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package