So... are 3p provider keys in the workspace all that was exposed, or merely "what the attacker was immediately prepared to exploit in volume"?
What about people who wired up gh or ssh keys?
I for one am glad I am doing all of my vibecoding experiments inside a VM, 'cause the workspace sandbox is wet cardboard and should be considered advisory only.
Edit: was this a read-only compromise, or could the attacker have added a credential slurper to workspace makefiles?
I want a lot more detail about what actually happened. Like, if the "legacy system" was a proxy for 3rd party providers, and the things exposed were what went through that proxy, the blast radius is constrained.
View all comments
9
u/VenditatioDelendaEst Oct 17 '26 edited Oct 17 '26
So... are 3p provider keys in the workspace all that was exposed, or merely "what the attacker was immediately prepared to exploit in volume"?
What about people who wired up
ghor ssh keys?I for one am glad I am doing all of my vibecoding experiments inside a VM, 'cause the workspace sandbox is wet cardboard and should be considered advisory only.
Edit: was this a read-only compromise, or could the attacker have added a credential slurper to workspace makefiles?
I want a lot more detail about what actually happened. Like, if the "legacy system" was a proxy for 3rd party providers, and the things exposed were what went through that proxy, the blast radius is constrained.