@cap-js/sqlite
Affected
- introduced
2.2.2, fixed2.3.0(semver)
Fixed versions
2.3.0
Fix
- Fixed version
2.3.0npm install @cap-js/[email protected]
Advisory
Also known as: CVE-2026-46421
Supply chain compromise via malicious package versions (@cap-js/sqlite, @cap-js/postgres, @cap-js/db-service)
Impact
On April 29, 2026, compromised versions of @cap-js/[email protected], @cap-js/[email protected], and @cap-js/[email protected] were published.
The malicious packages harvested credentials and attempted self-propagation.
If a compromised version was installed, all credentials accessible on that machine (npm tokens, cloud provider credentials, SSH keys, GitHub PATs) should be considered compromised.
Patches
Upgrade to @cap-js/sqlite >= 2.4.0, @cap-js/postgres >= 2.3.0, @cap-js/db-service >= 2.11.0.
If a compromised version was ever installed, rotate all affected credentials.
Workarounds
No workarounds.
Critical Basis: The source's own band: CRITICAL
2.2.2, fixed 2.3.0 (semver)2.3.0
2.3.0npm install @cap-js/[email protected]2.2.2, fixed 2.3.0 (semver)2.3.0
2.3.0npm install @cap-js/[email protected]2.10.1, fixed 2.11.0 (semver)2.11.0
2.11.0npm install @cap-js/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0