Malware in @sql-trigger/nodesql
Malware discovered in the npm package @sql-trigger/nodesql. 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
- @sql-trigger/nodesql
The npm package @sql-trigger/nodesql has been identified as containing malware. According to the GitHub Advisory (GHSA-9f9w-wg5j-m53j), 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 from a different, uncompromised system. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the package installation, given the potential for complete system compromise.\n\nThis represents a critical supply chain attack through a malicious package in the npm ecosystem.
Indicators of compromise
- Packages
- @sql-trigger/nodesql
Remediation
- Immediately remove the @sql-trigger/nodesql package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Conduct a full security audit of any system that had this package installed
- Review system logs for unauthorized access or activity
- Consider full system reimaging if the package was installed on production or sensitive systems
- Monitor for any indicators of compromise or data exfiltration
Sources
- GitHub Advisory GHSA-9f9w-wg5j-m53j · GitHub Advisory Database
Cite this entry
"Malware in @sql-trigger/nodesql." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 3, 2026; last updated July 3, 2026. https://supplychainattack.org/incident/malware-in-sql-trigger-nodesql-dzew98
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 epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - containedcritical
Malware in leb128x
The npm package leb128x was found to contain malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - containedcritical
Malicious code in checkout-desktop-total (npm)
The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.
npmCompromised package