· News · 5 views
Kingdom Come Developer Warhorse Studios Confirms Cyberattack on Company Systems
Warhorse Studios, the developer behind Kingdom Come: Deliverance, confirmed unauthorized access to its company systems and data. The investigation is ongoing and no project changes have been announced.
Warhorse Studios, the Prague-based developer behind Kingdom Come: Deliverance, has confirmed that it was the target of a cyberattack. The incident involved unauthorized access to company systems and company data. The studio says its investigation is still underway, and it has not yet said who is responsible or how much information was taken.
What was announced
In an official statement published on October 27, 2026, Warhorse said it is working with cybersecurity experts to secure its systems and assess the full impact of the incident. It is also coordinating with the relevant authorities. The statement is hosted on a dedicated security-incident page, which is featured as the top highlight on the studio's homepage, according to Gaming.net.
CEO Martin Frývaldský addressed the situation directly. "This is a serious incident for Warhorse Studios and everyone affected," he said, adding that the immediate priority is to secure systems and establish the full extent of the breach. He promised further updates "as soon as we responsibly can." As of the statement, no project changes have been announced, and the operational impact is still being assessed.
Key details
- Developer: Warhorse Studios, Prague, Czech Republic
- Known for: Kingdom Come: Deliverance
- What happened: Unauthorized access to company systems and company data
- Announced: October 27, 2026, in an official statement
- Response: Working with cybersecurity experts and coordinating with the relevant authorities
- Missing or unconfirmed: The identity of the attackers, which data was accessed, whether personal data belonging to employees, partners or players was affected, and whether any game schedules will change
What it means for developers
- Treat security as production work. Backups, access control and account offboarding need the same planning as a feature milestone. Small teams often postpone them until a breach forces the issue.
- Limit access to build and cloud accounts. Give each person access only to the repositories, build servers and asset stores they need, and turn on hardware-backed two-factor authentication wherever it is supported.
- Write an incident playbook now. Decide in advance who makes the call, where credentials are stored, how you would lock down accounts, and who needs to be told first.
- Protect unreleased material. Unannounced builds, source files and design documents are valuable targets. Keep them off personal devices and away from services that are publicly exposed.
- Communicate early, even when the answer is partial. Warhorse has said what it knows and promised more later. Indie teams should choose one honest channel for updates so rumors do not fill the gap.
Sources
Cover image: © Warhorse Studios.
