3 ms·
The problem is that everything is wrong here. Username is not a signature of malware by itself. There could be a ton of reasons why someone could have an accoun
by janoc 9y ago
The problem is that everything is wrong here. Username is not a signature of malware by itself. There could be a ton of reasons why someone could have an account like that on the machine - be it someone's name, maybe some AI project, perhaps a robotic feline, who knows.
Unfortunately, it seems that Valve's software doesn't bother to actually check whether the machine has any malware installed, it bans anyone who has any account on the machine that matches a regexp. Innocent or not, who cares, right?
How "effective" this approach is is very much documented by the fact that as soon as the botters caught wind of this they have changed the username they use and Valve can play a game of cat & mouse with them now.
It is not the first time Valve got caught by doing dumb/lazy stuff like this. E.g. Steam was known to erase your entire machine (or at least what your current user had access to - so most likely all you data) because of lazy programming and hardwired assumptions (see here: https://www.theregister.co.uk/2015/01/17/scary_code_of_the_week_steam_cleans_linux_pcs/ https://www.theregister.co.uk/2015/01/17/scary_code_of_the_w... ). Their response has been pretty similar too - "Works as intended, go away, we don't care".
Yay ...
- paulmd 9y ago> Username is not a signature of malware by itself Devoid of all context, no it's not. When a malware is known to exclusively use a particular and uncommon pattern, yes it is. If you remove all context then nothing is ever a signature of malware. Maybe there is a legitimate reason for a third-party program to be writing your memory or injecting DLLs, you never know! But in practice those are red-alert triggers for any anti-cheat.