cross-posted from: https://programming.dev/post/37902936
- Forensic report compiled by the research collective behind the takedown of Block Blasters— Credit: 1989 on X/Twitter.
- G DATA Report.
For anybody wondering what is going on with $CANCER live stream... my life was saved for whole 24 hours untill someone tuned in my stream and got me to download verified game on Steam
After this I was drained for over 32,000$ USD of my creator fees earned on pumpdotfun and everything quickly changed. I can't breathe, I can't think, im completely lost on what is going to happen next, can't shake the feeling that it is my fault that I might end up on street again or not have anything to eat in few days... my heart wants to jump out of my mouth and it hurts.
I won't rewatch this myself but I have added a clip from the stream after I noticed what has happened.
also I have succesfully (CTOed) my creator rewards and they have been redirected to safe device.
Source: rastaland.TV on X/Twitter— Private front-end.
More context:
Yesterday a video game streamer named rastalandTV inadvertently livestreamed themselves being a victim of a cryptodraining campaign.
This particular spearphishing campaign is extraordinarily heinous because RastaLand is suffering from Stage-4 Sarcoma and is actively seeking donations for their cancer treatment. They lost $30,000 of the money which was designated for their cancer treatment. In the steam clip their friend tries to console them while they cry out, "I am broken now."
They were contacted by an unknown person who requested they play their video game demo (downloadable from Steam). In exchange for RastaLand playing their video game demo on stream, they would financially compensate them.
Unfortunately, the Steam game was actually a cryptodrainer masquerading as a legitimate video game.
Source: vx-underground on X/Twitter— Private front-end.
Source: ZachXBT on X/Twitter— Private front-end.
Comments
I wonder how many people are taking your statement at face value without recognising the sarcasm...
It's not sarcastic. That's exactly how most of these platforms work behind the scenes. They run automated, dynamic and static analysis against all the app code looking for potentially harmful signatures.
Pretty sure Steam already does that. And no automated (or even manual) analysis is going to be 100% foolproof, or we wouldn't be worrying about supply chain attacks in Linux. So that puts us back at square one.
Yeah that's literally what I said. Seems like the previous guy didn't understand that. I don't know why anyone would downvote me for just explaining how it works.
I think because in the context of the discussion, you're (probably unintentionally?) making it sound like Steam is at fault for not catching the malware.
I mean that's explicitly what the document above says. They call it a colossal failure of valve to allow such incredibly brazen and malware to exist on their store. If you read the forensic analysis, the writers definitely are very much blaming valve for the breach.
Yes, and a lot of people disagree with them, because the authors are dumb.
I mean it's a pretty technical deep dive and they actually managed to uncover the bad guys and are willing to work with law enforcement to help see Justice done. Not exactly sure how you think they are dumb.
You can be smart on some stuff and dumb in others. Their dumb take was on somehow deciding valve was responsible without providing any sort of logical reasoning.
That's not analyzing the code. Also almost assuredly steam does that. Finally that wouldn't catch this since it was a back door, as long as the attacker didn't use it it would not be detected by any automated means.
That's called cloaking and you are right that it's not easy to find which is why you have to trip the payload with varied approaches. Reverse engineers generally are tipped off by suspicious code artifacts then start diving in. I guess the lesson here is that people really overestimated steam's capabilities at keeping out bad stuff and you should definitely never install any game that you're not familiar with.