Steam game CivIdle chat flaw pushed a trojan to Windows players
Part of the CivIdle story · since 16 Nov
- Mon 16 Nov, 00:08 UTC. cybersixt, first report. Steam game CivIdle chat flaw pushed a trojan to Windows players. This article, 1st of 1.
An attacker used the in-game chat of CivIdle, an open-source idle strategy game on Steam, to run malicious script on players' computers and install a trojan on Windows machines, its developer says. In a security advisory on Steam, the developer, Fish Pond Studio, said the attacker sent a specially crafted direct message at 00:40 UTC on 15 November that injected scripts into the game client, a cross-site scripting (XSS) attack.
How it worked
The game escaped chat messages in most of its interface, but not in the pop-up toast notifications that show new messages, the developer said, and the attacker used that gap. The flaw was not limited to direct messages; the attacker used DMs, a relatively new feature, to hide what they were doing. The developer said the attacker had tried and failed about a month earlier, then came back and bought the game's Supporter Pack to get around a chat limit. The attack is specific to CivIdle's own code, and the developer suggested that its public source code made it easier to find.
Players reported it on Discord at 00:40 UTC, a volunteer moderator stopped the attacker's account from chatting at 00:51, and DMs were switched off on the server at 01:18. A server-side fix that strips all HTML tags from chat messages went out at 02:08, and a client update, Build 1018, followed on Steam at 05:48; its code change is public. DMs will stay disabled indefinitely.
Who is affected
Only Windows players were affected, and antivirus software may have blocked the payload, though that is not guaranteed. The developer described the malware as a variant of a lesser-known generic trojan hosted on a German IP address, and has shared a sample on VirusTotal (SHA-256 cd80a99d6181cc0d9f4a738c5b9a7ec21cecf5ebf539a2481622e1fe755cc70d). It has not said how many players received the message.
What CivIdle players should do
Windows players who had the game running on 15 November should look for q.exe in the CivIdle installation folder, p.bat in C:\Users\Public, and a randomly named .exe file under AppData\Roaming\Microsoft\DeviceSync in their user folder. Any of them means the machine was very likely infected, though their absence does not prove it was not.
The developer advises updating antivirus definitions and running an offline scan, treating SSH keys, crypto wallets and API keys stored on the machine as compromised and rotating them from a clean device, signing out of Steam, Discord and other sessions used on that PC, enabling two-factor authentication, and considering a fresh Windows installation.
What is not known
It is not known how many players were infected, what the trojan does once installed, or whether the attacker was after particular players. The developer has reported the attacker's Steam account to Valve.
How the story developed
1 article from 1 outlet since 16 Nov. Still developing; the latest report was 23 hours ago. This was the first report.
- Mon 16 Nov, 00:08 UTC. cybersixt, first report. Steam game CivIdle chat flaw pushed a trojan to Windows players. This article, 1st of 1.
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 1 articles as a listHide the list
- Mon 16 NovDay 01
- Steam game CivIdle chat flaw pushed a trojan to Windows players00:08 · cybersixt · First report · This article, 1st of 1
Sources
More reporting
- Suspected Optimizely breach planted card stealer on 186 websites16 Nov
- BundID cyberattack locks German accounts, email codes now required16 Nov
- Trezor data breach at shipping partner exposes 27,000 orders16 Nov
- Fugaku supercomputer hit by cyberattack, users' SSH keys stolen16 Nov
- Lighter DEX exploit drains $10.4M via a trader's leaked API keys16 Nov
Written by CyberSIXT from the sources above.How we reportCorrectionsRSS