@cap-js/openapi
Affected
- introduced
1.4.1, fixed1.4.2(semver)
Fixed versions
1.4.2
Fix
- Fixed version
1.4.2npm install @cap-js/[email protected]
Advisory
Also known as: None
Supply chain compromise via malicious @cap-js/openapi
Impact
On May 19, 2026, a compromised version of @cap-js/[email protected] was 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/openapi >= 1.4.2
If the compromised version was ever installed, rotate all affected credentials.
Workarounds
No workarounds.
References
Critical Basis: The source's own band: CRITICAL
1.4.1, fixed 1.4.2 (semver)1.4.2
1.4.2npm 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