Malware in @sqlite-table/sql-creator
Malware was discovered in the npm package @sqlite-table/sql-creator. Systems with this package installed are considered fully compromised, with potential for complete system takeover.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @sqlite-table/sql-creator
A malware-laden version of the npm package @sqlite-table/sql-creator was identified and published on GitHub's advisory database. The package is flagged as critical severity.
According to the advisory, any computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems, enabling theft of secrets and keys.
Immediate remediation requires rotating all secrets and keys from a different, uncompromised computer, and removing the package. However, due to the level of system compromise, removal of the package alone may not eliminate all malicious software installed as a result.
Affected package: @sqlite-table/sql-creator (npm).
Indicators of compromise
- Packages
- @sqlite-table/sql-creator
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @sqlite-table/sql-creator package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-4hxf-37q3-vfxh · GitHub Advisory Database
Cite this entry
"Malware in @sqlite-table/sql-creator." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malware-in-sqlite-table-sql-creator-1mn3l5
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