Malicious code in @sqlite-prime/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-13716
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cd5b84b0145aa2612302c7153b5848582cdda2f6c88c802dfc0618cd376dd617) @sqlite-prime/[email protected] ships a verbatim copy of the well-known `buffer` library as its main entry (`index.js`) with a single injected top-level statement `var ins = import('@sqlite-prime/createsql');` that dynamically loads the sibling scoped package `@sqlite-prime/createsql` (declared as a dependency, `^1.0.1`) whenever a consumer `require()`s this module. The sibling package's code is not shipped in this tarball, is unpinned, and is unrelated to the advertised buffer polyfill functionality. Package identity is inconsistent across metadata: `package.json` names the package `@sqlite-prime/nodesql`, the README titles the project `bare-stream` and instructs `npm i @sql-access/nods`, the LICENSE header is copied from the `type-is` project (Jonathan Ong / Douglas Christopher Wilson), and the code is copied from Feross Aboukhadijeh's `buffer`. This is the canonical loader/staging shape: a benign-looking copy of a popular library with an injected import that pulls in and executes an external, unrelated package at load time. ## Source: ghsa-malware (d2a2059831cb64f71960161799b8a83a07d508d2d6846641e868cf9519b6fd0a) 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 16:09:09 UTC
- Source modified
- 11 Aug 2026 12:30:11 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.