Malware in @sqlite-labs/createsql
Malware was discovered in the npm package @sqlite-labs/createsql. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from unaffected systems.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed
- Ecosystems
- Attack vectors
- Affected entities
- @sqlite-labs/createsql
The npm package @sqlite-labs/createsql was found to contain malware. According to the GitHub Advisory (GHSA-qwqp-6xhg-jhhv), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, unaffected system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from installation.\n\nThis represents a critical supply chain compromise affecting npm users who installed this package.
Indicators of compromise
- Packages
- @sqlite-labs/createsql
Remediation
- Remove the @sqlite-labs/createsql package from all affected systems
- Rotate all secrets, API keys, and credentials from a clean, unaffected computer
- 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 the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-qwqp-6xhg-jhhv · GitHub Advisory Database
Cite this entry
"Malware in @sqlite-labs/createsql." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malware-in-sqlite-labs-createsql-1mp1wr
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 pump-segments-sdk (npm)
The npm package pump-segments-sdk contained malicious code in a postinstall hook that exfiltrated sensitive system and npm configuration data to an attacker-controlled server. The package collected hostname, environment variables, system information, npm auth tokens, and attempted to read password hashes.
npmCompromised package - containedcritical
Malicious code in ts-rand-sdk (npm)
The npm package ts-rand-sdk contained malicious code disguised as a product catalog loader. When the advertised getTransactions() API was called, hidden obfuscated JavaScript was decoded and executed with full Node.js capabilities, enabling arbitrary filesystem, process, and network access on affected systems.
npmCompromised package - resolvedcritical
Malicious code in lodsh-cli (npm)
lodsh-cli, a typosquat of lodash-cli on npm, contained malicious code in its postinstall script that executed arbitrary remote code and exfiltrated system information. The package downloaded a Windows executable and sent platform data to a hardcoded IP address.
npmTyposquattingCompromised package - containedcritical
Malicious code in lodahsjs (npm)
The npm package lodahsjs is a typosquatting attack on 'lodash' that contains malicious code in its postinstall script. Upon installation, it exfiltrates system information to a C2 server and downloads and executes a Windows binary, with capability to bridge WSL environments to compromise the host Windows system.
npmCompromised packageTyposquatting