Impact
On April 29, 2026, compromised versions of @cap-js/sqlite@2.2.2, @cap-js/postgres@2.2.2, and @cap-js/db-service@2.10.1 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.
References
patricebender Remediation developer
chgeo Finder
Impact
On April 29, 2026, compromised versions of
@cap-js/sqlite@2.2.2,@cap-js/postgres@2.2.2, and@cap-js/db-service@2.10.1were 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.
References