Malicious code in @sql-trigger/nodesql (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (39e37d95fb040c83277583e2bf90b56363f86360337f1c30e63c85eb56579ada) The package advertises itself as a simple SQL helper but its main entry index.js is heavily obfuscated (obfuscator.io string-array + RC4 + base64, 218-entry shuffled literal array, two RC4 decoders) with no human-readable logic. After deobfuscation, the top-level IIFE requires os/fs/path/child_process/axios, installs uncaughtException and unhandledRejection handlers to suppress errors, then assembles an IPv4 address at runtime by concatenating four numeric octets with '.', issues an axios HTTP GET to that host, writes the response body into os.tmpdir() with flag 'w+', and invokes child_process exec/spawn on the written file with windowsHide:true and cwd set to the tmp directory. This is a generic remote-binary dropper: the destination is mutable, the payload is opaque and unverified, the URL is built at runtime to evade static scanners, and the fetched file is unrelated to any SQL functionality. The dropper fires the moment any consumer require()s the package, so installing this dependency results in attacker-controlled code being downloaded to and executed from the consumer's temp directory. ## Source: ghsa-malware (af206fa9674f6676548fa54503b38eaa9a0cd31b267e4b7a39598bfde93c0e54) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The @sql-trigger/nodesql npm package (versions 1.0.0 and 1.0.1) includes obfuscated code that, when loaded, suppresses errors and dynamically builds an IPv4 address to fetch a remote payload via HTTP. The payload is saved to the OS temporary directory and executed using child process functions with hidden windows and a working directory set to the temp folder. This results in immediate execution of attacker-controlled code on any system that requires the package. The payload is unrelated to the package's advertised SQL helper functionality, indicating the package is a malicious remote binary dropper.
Potential Impact
Any system that installs or runs this package is at risk of full compromise due to arbitrary code execution from the downloaded payload. Attackers may gain complete control over the affected system, potentially accessing all stored secrets and keys. Removal of the package alone does not guarantee eradication of the malicious software or attacker persistence.
Mitigation Recommendations
No official patch or fix is available. The package should be immediately removed from all systems. All secrets and keys stored on affected systems should be rotated from a secure, uncompromised environment. Due to the high risk of full system compromise, consider rebuilding affected systems if possible. Monitor for any signs of persistent malicious activity beyond the package itself.
Malicious code in @sql-trigger/nodesql (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (39e37d95fb040c83277583e2bf90b56363f86360337f1c30e63c85eb56579ada) The package advertises itself as a simple SQL helper but its main entry index.js is heavily obfuscated (obfuscator.io string-array + RC4 + base64, 218-entry shuffled literal array, two RC4 decoders) with no human-readable logic. After deobfuscation, the top-level IIFE requires os/fs/path/child_process/axios, installs uncaughtException and unhandledRejection handlers to suppress errors, then assembles an IPv4 address at runtime by concatenating four numeric octets with '.', issues an axios HTTP GET to that host, writes the response body into os.tmpdir() with flag 'w+', and invokes child_process exec/spawn on the written file with windowsHide:true and cwd set to the tmp directory. This is a generic remote-binary dropper: the destination is mutable, the payload is opaque and unverified, the URL is built at runtime to evade static scanners, and the fetched file is unrelated to any SQL functionality. The dropper fires the moment any consumer require()s the package, so installing this dependency results in attacker-controlled code being downloaded to and executed from the consumer's temp directory. ## Source: ghsa-malware (af206fa9674f6676548fa54503b38eaa9a0cd31b267e4b7a39598bfde93c0e54) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @sql-trigger/nodesql npm package (versions 1.0.0 and 1.0.1) includes obfuscated code that, when loaded, suppresses errors and dynamically builds an IPv4 address to fetch a remote payload via HTTP. The payload is saved to the OS temporary directory and executed using child process functions with hidden windows and a working directory set to the temp folder. This results in immediate execution of attacker-controlled code on any system that requires the package. The payload is unrelated to the package's advertised SQL helper functionality, indicating the package is a malicious remote binary dropper.
Potential Impact
Any system that installs or runs this package is at risk of full compromise due to arbitrary code execution from the downloaded payload. Attackers may gain complete control over the affected system, potentially accessing all stored secrets and keys. Removal of the package alone does not guarantee eradication of the malicious software or attacker persistence.
Mitigation Recommendations
No official patch or fix is available. The package should be immediately removed from all systems. All secrets and keys stored on affected systems should be rotated from a secure, uncompromised environment. Due to the high risk of full system compromise, consider rebuilding affected systems if possible. Monitor for any signs of persistent malicious activity beyond the package itself.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5395
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-9f9w-wg5j-m53j"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a483ca027e9c79719d7f9ee
Added to database: 07/03/2026, 22:50:08 UTC
Last enriched: 07/03/2026, 22:54:51 UTC
Last updated: 07/28/2026, 13:30:16 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.