Malware in @sqlite-prime/createsql
Malware discovered in the npm package @sqlite-prime/createsql. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @sqlite-prime/createsql
A malicious npm package, @sqlite-prime/createsql, has been identified as containing malware. According to the GitHub Advisory (GHSA-v49c-g99c-qvf9), any computer with 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 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 the attacker may have gained full control of the system.\n\nUsers should treat any system that has run this package as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- @sqlite-prime/createsql
Remediation
- Immediately remove the @sqlite-prime/createsql package from all systems
- Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
- Assume full system compromise and perform forensic analysis or rebuild affected systems
- Audit logs and monitor for unauthorized access or lateral movement from affected systems
- Check npm audit logs and package.json files to identify all systems where this package was installed
Sources
- GitHub Advisory GHSA-v49c-g99c-qvf9 · GitHub Advisory Database
Cite this entry
"Malware in @sqlite-prime/createsql." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malware-in-sqlite-prime-createsql-19z9f8
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