[ad_1]
The Team Fortress 2 source code apparently leaked, prompting hackers to reportedly deliver malware through remote code execution to other players.
Initially, @SteamDB reported on Twitter about this leak, with the source code in question from 2017 and 2018, which affects Counter-Strike: Source and Team Fortress 2. According to a report on the PCGamesN problem, several Team Fortress 2 servers Communities have advised players to avoid the game until further notice.
The source code for CS: GO and TF2 dated 2017/2018 that was made available to licensees of the Source engine was leaked to the public today. pic.twitter.com/qWEQGbq9Y6April 22, 2020
We have reached out to Valve to comment on this situation, and will update this story as soon as we hear anything. However, according to @HeavyUpdateOut On Twitter, “Remote code execution vulnerabilities have already been found.” However, it’s important to note that @HeavyUpdateOut is just a fan account, and while it’s incredibly popular, you should take advantage of the damage with a grain of salt.
Do not start TF2 under any circumstances, remote code execution vulnerabilities have already been found, which means you can get a virus by simply joining a server with a cheat. This is not a drill.April 22, 2020
Still, neither Valve nor Team Fortress 2’s Twitter accounts have shared news on this topic, and the company hasn’t posted anything on its own forums or the Team Fortress 2 subreddit. Instead, the community has taken up front, with a post on the TF2 subreddit warning users not to play TF2 or CS: GO until the issue is fixed. That post says, “If you are not playing on any multiplayer server, you are not at risk,” but it may be best to avoid affected games entirely.
We are also hearing unconfirmed reports that all current multiplayer source based games may be affected, including the Garry Mod.
Until Valve comes out and makes a statement or updates the game in some way, this is not confirmed. But since this is potentially a danger to the security of your data, our advice would be to avoid playing until Valve has properly addressed the issue.
We’re going to be doing a little more research on our part as well, and we’ll update as soon as we get more information. Until then, maybe it’s time to take a look at one of the best PC games just to play safely for now.
This is a developing story.
Why is this so dangerous?
We have to reiterate that reports of Remote Code Execution in Team Fortress 2 and other Valve games have not been confirmed. In fact, in the Reddit thread we mentioned earlier, the Demoman mod clarifies that the source code is “an old version and was leaked initially a year or two ago.” And also that “it is unlikely but not impossible that there are security flaws like RCE (Remote Code Execution). ”
Still, CER risk in the first place is a pretty substantial threat. Through this particularly nasty flavor of malware, an attacker can gain full control of your PC and execute any code without your permission.
Wannacry was a pretty prime example of a cyberattack enabled through RCE last year. This was a piece of ransomware that encrypted all the files on the victims’ PCs, demanding substantial payment through the cryptocurrency.
So even if RCE has not been actively confirmedThe fact that it is even a possibility in the current state of the game means that it is best avoided. If an attacker can do it, all of your data is potentially at risk.
[ad_2]
