On November 15, 2026, at 00:40 UTC, a malicious actor (Steam ID: 76561198610776106, IP address: 23.234.88.59) exploited a vulnerability in the game client by sending a specially crafted direct message (DM). The message injected malicious scripts, resulting in a cross-site scripting (XSS) attack.
Timeline (UTC)
- 00:40 The first player report was received on Discord.
- 00:51 A moderator (MAURER) banned the attacker from sending further chat messages.
- 01:08 I became aware of the issue and began investigating.
- 01:18 DMs were disabled on the server as an immediate mitigation.
- 02:08 A server-side fix was deployed.
- 03:15 An optional client-side fix was ready for deployment. The server-side fix addresses the vulnerability; the client-side fix provides an additional layer of protection.
- 05:48 The optional client-side fix (Build 1018) was deployed via Steam. Deployment was delayed because I needed to accept a new Apple Developer Agreement.
Root Cause
Chat messages were escaped in most of the game's UI, but not in toast notifications. The attacker exploited this gap to inject malicious scripts.
The server now strips all HTML tags from chat messages as a safeguard against cases where the client fails to escape them. The client-side fix can be reviewed on GitHub.
The vulnerability was not specific to DMs - the attacker used DMs to conceal their activity. As a precaution, I have disabled DMs indefinitely so that similar incidents can be detected and addressed more quickly.
Impact
This attack affects Windows only. Windows Defender or other antivirus software may block the malicious file from running, but this is not guaranteed.
To check for signs that your system was affected, look for these files:
- q.exe in your CivIdle installation folder. The location depends on your Steam library settings; the default is C:\Program Files (x86)\Steam\steamapps\common\Cividle.
- p.bat in C:\Users\Public.
- The Trojan also generate a randomly named file in C:\Users\\AppData\Roaming\Microsoft\DeviceSync\.exe
If any file is present, your system was very likely affected. Their absence does not guarantee that your system is unaffected.
I am not a security expert. If you can seek help from a security professional, please do. Here are my suggestions:
- Update your antivirus software and its threat definitions, then run an offline virus scan. I have submitted the sample to VirusTotal.
- Remove all malicious files, if present. Boot into Safe Mode if necessary, and check your system's startup entries for anything suspicious.
As additional precautions:
- If you store sensitive credentials or assets on the machine, such as SSH keys, cryptocurrency wallets, or LLM API keys, consider them potentially compromised. From a trusted device, rotate affected credentials and take appropriate steps to secure your assets.
- Enable two-factor authentication (2FA) on your accounts.
- Revoke existing sessions for Steam, Discord, and other accounts used on the machine. Sign in again only after the system has been secured.
- Consider a fresh re-installation of Windows to be extra cautious.
I have submitted the malware sample to major antivirus vendors and reported the attacker's Steam account to Steam. You can also report the account by visiting the Steam profile and selecting More → Report Player.
Personal Notes
This was definitely a carefully planned attack. The attacker tried a while ago (maybe a month?) but failed. They then came back with a new attack - even purchasing a Supporter Pack to get around the chat limit and using DMs, a relatively new and obscure feature, to try to conceal their activity. The vulnerability isn’t generic; it’s specific to this game’s code.
Given that we’re a small, lesser-known idle game, putting in that much effort seems unjustified unless the attacker had specific targets in mind. Or perhaps, because the game is open source, the attacker used AI to plan the attack. Having access to the source code definitely made it easier.
The Trojan appears to be a variant of a generic, lesser-known Trojan, hosted at a German IP address, but I wasn’t able to determine much beyond that. The attacker logged into the game using a US IP address, probably through a VPN or something similar.
For those of you who have been affected, please accept my sincere apology. I do my best to ensure the game's code is secure. The decision to open-source the game's code was made before AI developed coding and cybersecurity capabilities. If you have discovered a vulnerability, please contact me at hi @ fishpondstudio . com, and I will get back to you as soon as I can.
Finally, I want to express my gratitude to the moderation team, especially MAURER, for taking prompt action and managing to limit the damage. Moderation is handled by community volunteers. Sometimes they have to make tough decisions and cannot make everyone happy, but their work is essential to keeping the community safe and healthy.
