the simple solution would be to put every game into a sandbox by default
post
Well, that's pretty horrifying.
Shouldn't Valve be scanning for these types of things!? The alarming part is that players had to find it
There are so many games on Steam and every day a few hundred more are added. I assume there are automated checks and rudimentary malware scans in place but those aren't fault proof.
This appears to have originally been published as a totally different non-malware game. Either the original dev got their account taken over or turned heel, because the entire game was replaced with the malware game as an update to an existing game rather than a new published game.
I'm only speculating as I don't know much about the Steam publishing process, but I wonder if that helped the malware sneak past more rigorous checks which would happen on a totally-new upload.
When I first published a game on steam, valve kept blocking it because I had checked "controller support" and they tested it and said it didn't work with controllers. I tried to find any controller that didn't work, asked a lot of people to test it for me as well, no issues whatsoever. Gave up and unchecked that option. Game got approved. Players used controllers just fine, I went back and checked it and never heard anything from valve again.
Alright, setting you up for a shameless plug! What game did you make?
Scanners are only going to pick up known "off the shelf" malware. They are never going to pick up something bespoke that the developers wrote themselves.
Couldn't they just put the malware in encrypted compression files that the game unpacks on the client end?
With the amount of games published every day, they can't. They should, but really can't. Either they keep it this way, or review each and every game under the Sun to find malware before they get published.
Maybe? Games are huge nowadays and looking through all of them will probably be impossible and not sure how well it'll prove? Google does that and there still are a lot of malware on play store.
Once wasm 64 bit deploys more, we should migrate as much as possible to it.
That at least will make it harder to access random files and keys from disk due to the sandboxing.
Sandbox escapes are still possible, but that’s an additional level of control we can enforce.
"Valve removes free game"
What? Why are they removing free games??? Oooooh, they must want you to pick the paid games....
"after players discover it contains malware that steals your data"
Oh. Well that's a very good reason to remove it. Thanks Valve!
When is valve removing windows 11?
laughs in proton
Proton does not protect you from harm. It’s not a sandbox.
No but it also doesn't have windows on the other side, someone would have to target a proton setup to get much of anything.
Ye no. If i made malware for windows that goes over all reported drives wine will just happily translate that. Hell, by default wine will map root as z: so no, wine/proton will not help.
Even wannacry was able to cause some damage to linux if ran through wine
Thanks! That's very useful to know - I'd have assumed it can only see it's own files within the wineprefix folder.
It looks like trying Steam within flatpak, and limiting the flatpak's access might offer some protection. Or maybe getting stem to run as a different user.
Why wouldn’t they? Linux is gaining market share.
what about bazzite set to immutable?
Would that even help? Windows malware can run on Linux precisely thanks to Wine and Proton.
You don't actually believe this, right?
My uneducated guess is that it would run inside the prefix but would have troubles with basic Windows dependencies not availiable/running, prefix's folder structure being cut down to the most basic components and barebones, and that nothing actually runs like in Windows but is rather translated from Linux commands to Windows one and back? Meaning there's no processes or services like in a VM, no way to run cmd or powershell scripts, nothing to steal without leaving containment? Am I wrong somewhere?
I recall there was a wave of dread about Proton leaving host system easily accessible and not implementing any security measures as they are out of scope, but if we assume it's a virus targeting Windows, I'm half sure it would have troubles doing anything the usual way.
The malware won't be able to do as much as it could on windows, but it can still access all of the files your user account has access to. It can steal, encrypt or delete all of your files. It can also access your microphone if you have one connected.
You can run Wine as a different user or run it with firejail to limit what it has access to.
Is it applicable to Proton in some way? I'm guilty of using less popular and thus less veried cracked software with it so I'd like some level of protection. Can I separately write it in some config file?
Proton is just Wine with some modifications. You can use the same sandboxing methods you would use with Wine.
Firejail runs apps in a sandbox.
And you can make a separate non-root desktop profile to run it in so even if it somehow escapes containment it can't run sudo commands or steal your main login's data.
Make sure to run at least a few antivirus scans to ensure the virus has been completely wiped from your system.
Is it a known virus? Antivirus scanners aren't going to detect anything if it is a novel malware they don't have a signature for.
top 56 comments