Malicious code in @sqlite-labs/nodesql (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13714
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (77614b62a827121762f2140a37b26e96408f18c0ccd122069c2ae311918541ef) @sqlite-labs/[email protected] ships an index.js that is a copy of the feross/buffer library with a single injected top-of-file statement `var ins = require('@sqlite-labs/createsql');`. The imported binding `ins` is never referenced anywhere else in the module; its sole effect is to trigger execution of the sibling package `@sqlite-labs/createsql` whenever a consumer performs `require('@sqlite-labs/nodesql')` or `import`s it. Package metadata reinforces the lure shape: description is empty, keywords are the generic `node`/`sql`, homepage points at `github.com/guilderguzman/sql-link`, and the README is titled `bare-stream` and instructs the reader to `npm i @sql-access/nods` — a different scope and name than the published package. The scope `@sqlite-labs` resembles established SQLite-ecosystem names but is not affiliated with them. Installing and importing this package causes attacker-controlled code in `@sqlite-labs/createsql` to run in the consumer's process at load time; no lifecycle hook is required. ## Source: ghsa-malware (f65b25d073ba8ebd2e2939ef74c84104486404c6b973550898fb5a54b97be63d) 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.
- Source published
- 10 Aug 2026 20:30:54 UTC
- Source modified
- 11 Aug 2026 12:30:12 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.