An attacker turned the in-game chat of CivIdle, a free-to-play idle civilization game on Steam, into a malware delivery channel. According to the developer's own security advisory, a single specially crafted direct message was enough to run malicious scripts on players' Windows PCs on November 15, 2026, and drop a trojan.
What happened
The attack was a classic cross-site scripting (XSS) bug inside a game client. The developer explains that chat messages were escaped in most of the game's interface, but not in toast notifications — the small pop-ups that appear when a new message arrives. The attacker hid code inside a DM, and when the notification rendered it, the code ran on the player's machine.
The response was fast. Per the advisory's timeline (UTC):
- 00:40 – first player report arrives on Discord
- 00:51 – a moderator bans the attacker from chat
- 01:18 – DMs are disabled on the server
- 02:08 – a server-side fix that strips all HTML from chat messages goes live
- 05:48 – an optional client-side fix, Build 1018, ships through Steam
The developer says the flaw was not specific to DMs; the attacker used them to stay out of sight, and DMs are now disabled indefinitely. Only Windows players are affected.
Why it matters
Many modern games are built on web technology, which means a chat window can behave like a web page. If any part of that interface renders player text as code, every message becomes a potential exploit, and players never have to click anything. This is the same bug class that has hit websites for decades, now landing on gaming PCs that often also hold Steam and Discord sessions, crypto wallets and developer keys.
What players should do
- Update CivIdle and run a full offline antivirus scan with fresh definitions.
- Check for the infection signs the developer lists: q.exe in the CivIdle install folder and p.bat in C:\Users\Public.
- From a clean device, revoke Steam, Discord and other sessions, enable two-factor authentication, and rotate SSH keys, API keys or wallet secrets stored on the PC.
- If infection signs are present, consider a fresh Windows install.
The builder takeaway
Escape untrusted text on every screen, not most of them.
Notifications, tooltips, logs and admin panels are where escaping is most often forgotten. The developer's second fix is also a good pattern: sanitize on the server too, so one client-side slip can't become a remote code path.




