This could have been avoided by having extensions signed by company doing them with keys and review
On publishing, I do see that the MS marketplace has much better typosquatting and rogue publisher protection. It's unclear to me how much better their SAST/scanning is than OpenVSX. Both have something, but both have been fooled many times, and recently.
Binance got a pretty expensive lesson if that was the cause for their recent hack
Why risk getting compromised like that?
Edit: It seems Cursor is claiming the tampered files were only in their mirror.
> Dworken from Anthropic here, that is correct: This only impacted the extension as it was hosted on the Cursor marketplace. It did not impact the official VS Code extension marketplace or OpenVSX. Users of Claude Code on VS Code are not impacted by this issue.
https://github.com/eclipse-openvsx/openvsx/wiki/Trusted-Publ...
Edit: Ah, guess it was not open-vsx, but a in-house Cursor marketplace. https://news.ycombinator.com/item?id=50304129
Anthropic's position is seemingly that it was "another part of the publishing process [that] was compromised"
Vibecoders are safu
Igor Kofman: "I do not write any code by myself anymore."
Turns out if you are not writing the code, then North Koreans might do it for you