Vulnerability
Malicious code in @sql-access/nodesql (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2acee7592879b9eab377fb8e97a1fa2949b298f4418d37fb963e157971638c90) @sql-access/nodesql@1.1.3 is a decoy package whose identity, README, and code do not match. The package name and keywords advertise SQL/Node functionality; the README is copy-pasted from an unrelated 'bare-stream' streaming library and points to github.com/guilderguzman/sql-link; index.js is a verbatim copy of the feross/buffer Buffer polyfill. A single statement has been injected as the first executable line of index.js: `import('@sqlite-node/createsql');`. As a result, any consumer that does `require('@sql-access/nodesql')` will asynchronously load and execute the top-level code of @sqlite-node/createsql, an unpinned (`^1.0.5`) separately-published package in an attacker-namespaced scope that has no relationship to a Buffer polyfill or to the package's stated SQL purpose. The decoy code itself performs no SQL work, no Buffer functionality is reached by the consumer in any meaningful way, and the only practical effect of installing or requiring this package is to silently pull a different, attacker-controlled module into the installer's dependency graph and execute it at import time. The combined identity confusion (name/README/code mismatch), namesquat-shaped transitive (`@sqlite-node/createsql`), unpinned caret range, and bolt-on dynamic import injected into otherwise-pristine upstream source match the documented loader/decoy supply-chain pattern.
No CVSS base score from NVD or GHSA yet. NVD typically scores within 24–72 hours of publication; GHSA usually within a day for OSS-flagged CVEs. Last record update .
For interim severity, fall back on KEV / EXPLOIT signals and the EPSS percentile (lower panel). Re-check this CVE after one cron tick — the score lands automatically when the source publishes.
FIRST.org publishes EPSS daily. Coverage isn't universal — pre-disclosure CVEs and reserved IDs don't carry an EPSS score until at least one exploitation signal lands. Score will appear within 24 hours of the next EPSS pull.
No exploitation, limited impact or prevalence