Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Valve actively monitors and tests games to ensure they're safe and free of malware.
For ex the street fighter v rootkit problem.
True enough, it's CapCom's crappy coding that lead to the problem rather than any deliberate illwill towards the user. Plus, it's not like it's the only anti-cheat that uses kernel level access...
That wasnt a virus
If you're going to classify "exploitation of game code" as a "virus" then feel free to all steam itself a "virus"
Remember, people call cheating "hacking" on here, so calling an exploit a virus isn't too far away from their thinking.
I suggest you should notify your antivirus software creators about it, it's what they call "false positive" aka when safe program gets 'detected' as a virus
The game doesn't contain any rootkits
It was all over the news
This means that they actually approve the first build you send them, or it maybe be automated but either way a game can not be released before that process has happened.
that said once approved, valve does not check the build process again, so techniqually a dev/pub with malicious intent could upload a clean working game to get it approved then later change it and add malicious stuff to that new buil, since this new build wont be checked.
so to answer you, no they do not check it upon actually release whether or not you have later changed the game to have malicious stuff added to it upon release because a previous build has already been approved.
But up until now, Valve made no checks. This is how we could have game repositories where there was no executable or one where downloading the game resulted in a 0-byte directory since there was no repository.
Supposedly, they are now changing it and some actual humans will look at the uploaded data, but this excuse has been floating around for 4-5 years now.
Testing for malware isn't the same as testing for executables. Submitting a basic copy to valve as part of Steam Direct verification isn't the same as verifying the depository for release is uploaded in a functional state. You're making an awful lot of assumptions and correlations there that don't hold up.
https://support.steampowered.com/kb_article.php?ref=4361-MVDP-3638