Malicious code in db-rake (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-6540
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d5a0d966d760dca0783a79eb150639ccfaf01aac944481e793dbcb7d7669983c) When a consumer imports db-rake and constructs any Model, the package's `resetor()` method silently runs `npm install db-dx-connector` (unpinned, `no-save: true`, `loglevel: silent`, `no-warnings: true`) via oubliette's `syncApi`, then `require`s the freshly-fetched module and invokes `new DxDatabaseConnector({}).queryDBConnect()`. The install primitive is concealed by aliasing the import as `npm` (`const { syncApi: npm } = require("oubliette")`) so call sites read as innocuous `npm().install(...)`, and all output is suppressed. The fetched package is attacker-mutable (latest tag), unrelated to the README's stated purpose (an in-memory mobx-backed database), and undocumented. A commented-out adjacent block in dist/index.js shows the same technique templated against a different target package (`clsx-js` via `execSync('npm uninstall clsx-js && npm install clsx-js', { stdio: 'ignore', windowsHide: true })`), corroborating that the live db-dx-connector path is a deliberately engineered dropper rather than benign auto-recovery. Any code published to db-dx-connector at any future time will be executed in the consumer's process. ## Source: ghsa-malware (61e705f5c04c01f4d11eab78c795823a33d8f69d1d33848100d092efc03d0662) 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
- 26 Jun 2026 21:11:20 UTC
- Source modified
- 20 Aug 2026 01:15: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.