The Bitwarden security team identified and contained a malicious package that was briefly distributed through the npm delivery path for @bitwarden/cli@2026.4.0 between 5:57 PM and 7:30 PM (ET) on April 22, 2026, in connection with a broader Checkmarx supply chain incident. The investigation found no evidence that end user vault data was accessed or at risk, or that production data or production systems were compromised. Once the issue was detected, compromised access was revoked, the malicious ...
If your assumption is that X509 is trash, does that mean you hold the same amount of distrust to TLS?
How do you propose the scaling of key management? Do you have a reasonable alternative to users blindly trusting every single key they come across?
Back to my original question: what prevents a VSCode extension from stealing a private signing key (as opposed to an API key) and causing the same issues described here?
With cryptography. X.509 is trash. They should pin the public key.
TLS is fine with certificate pinning m
That still leaves two out of three questions unanswered. Most importantly the last one, which was addressed towards the original complaint.