That's unlikely because Cursor (and VS Code) enforce a 12h delay for all extension updates by default. Malicious extension was only live for 11h so you shouldn't be affected unless you reduced it.
replyIn any case running an agent framework in anything but a strict environment like openshell or a VM with a non rooted container and with a firewall out side of that containment is the definition of stupidity.
replyThe supply chain attack had a software bug which raised error messages that were discovered by a security vendor. I don't think those people have the skills needed to elevate their initial access to a full binance compromise within a few hours.
replyRecency bias. I don’t see much evidence that the two things are related other than the coincidental timing.
replyIsn't the anthropic hack a day late?
replyIs it?
replyCursor's security announcement was posted on Oct 29 and says that the malicious extension was live "between about 2:27am PT and 1:35pm PT today"
This article says the attack took place "on Thursday" (which means Oct 29) and began at 4pm ET (which is 1pm PT)
and Binance has been tweeting that the cause of the hack may be a compromised employee laptop. yikes
The article also claims they had 36h to prep the attack, I assume this was the 36h prior to Thursday- if so unlikely to be related.
replyGood question, would be interesting to see an exact timeline on both side-by-side (confirmed events, not reporting).
reply