Comment by K0nserv
1 day ago
If the sole purpose of this hack was to steal cryptocurrency, a silver lining might be, as in many similar cases, that if you stay away from that particular dumpster fire you are probably okay. I mean there's still a reverse shell on your machine to fix, but at least nothing of value was lost.
Even if you don't have cryptocurrency they can still go after your GitHub credentials and run some very expensive agent and runner workloads.
I've started developing with a separate user account to limit the blast radius but you still need to login to access repos and use AI features.
For sure sandboxing and isolation is feeling increasingly relevant regardless, but crypto theft is acting as a good sponge.
now I kinda wanna shadow the usual SSH creds files with LLM read-only user, so it can rummage thru the repos all it wants but I need to do the push using my creds.
That's why I stay away from that dumpster fire too!
[dead]
I suppose it's just the best ROI on using a complex attack vector or spending one or more zero days. But other types of targets may wreak havoc for bystanders that become collateral damage, idk trying to get specific private info on a target may expose data on millions, or anything increasing scope as to hide the real target, etc.