Warhorse Studios has confirmed unauthorized access to company systems and data, leaving players waiting for answers on scope, personal information, and any impact on Kingdom Come production.
Image: mezha.net
Warhorse confirms unauthorized access, but the scope is still under investigation
Warhorse Studios has confirmed that it was targeted by a cyberattack involving unauthorized access to company systems and company data, according to the studio’s official statement cited by GamingOnLinux and GamesIndustry.biz. The Kingdom Come: Deliverance developer said it is working with cybersecurity experts to secure its systems, investigate the incident, and assess the full impact of the breach.
That confirmation is the hard center of the story. This is not a vague warning about suspicious activity or a precautionary outage. Warhorse has publicly acknowledged both systems access and data access. At the same time, the studio has not said what data was reached, when the intrusion happened, how the attackers got in, whether ransomware was involved, or whether any player information was affected.
CEO Martin Frývaldský described the event as “a serious incident for Warhorse Studios and everyone affected,” according to the statement published by the studio and quoted by multiple outlets. He said Warhorse’s immediate priorities are securing systems, establishing the full extent of the breach, and taking steps to protect employees, partners, and the community. Warhorse also said it is coordinating with relevant authorities as the investigation continues.
What Warhorse has said, and what it has deliberately not said
Warhorse’s public communication is narrow, which is common during an active security investigation but leaves important questions unresolved for players. The studio has confirmed the Warhorse Studios cyberattack, confirmed unauthorized access to company systems, confirmed access to company data, and confirmed that cybersecurity experts and relevant authorities are involved. It has also said it will share further verified information when it can do so responsibly.
Just as important is what remains unconfirmed. Warhorse has not identified the affected systems. It has not said whether development infrastructure, employee records, partner materials, internal builds, source repositories, payment details, account information, support databases, or community data were involved. Twisted Voxel reported that the studio had not disclosed the timing of the attack, the systems affected, the nature of the attack, or whether player information, internal files, or unreleased projects were accessed.
There is a small but important distinction in the reporting. Twisted Voxel’s wording says Warhorse had “yet to disclose what happened or whether any data was compromised,” while the official statement quoted by GamingOnLinux and GamesIndustry.biz says the attack involved access to company data. The safest reading is that Warhorse has confirmed company data was accessed, but has not confirmed which categories of data were involved or whether data was copied, leaked, altered, or used in any follow-up attack.
Players do not yet have a confirmed account-risk answer
For Kingdom Come players, the practical concern is whether this is a studio-side incident only or whether it reaches personal information connected to accounts, support tickets, newsletters, forums, testing programs, or purchasing platforms. The sources provided do not confirm any player account compromise, password exposure, payment-data access, or store-account issue tied to the Warhorse data breach.
That absence of confirmation cuts both ways. It means players should not assume their personal information was involved based on the current public record. It also means they should not treat the question as resolved. Warhorse’s own language says the full impact is still being assessed, and Frývaldský said the studio is still working to establish the full extent of the breach.
The sensible approach for players is to watch Warhorse’s official channels for verified follow-up rather than rely on screenshots, paste sites, or social posts claiming to show stolen material. Since Warhorse has not issued player-facing instructions in the source material, there is no confirmed requirement to reset a Warhorse-specific password or take a particular account action. General caution still applies around phishing, especially after a public breach, because attackers often exploit confusion around security incidents even when the original breach details remain unclear.
A breach at an RPG studio carries production questions even before any delay is confirmed
Warhorse is closely tied to large-scale RPG production through Kingdom Come: Deliverance and Kingdom Come: Deliverance II. GamesIndustry.biz identifies the studio as the Kingdom Come: Deliverance 2 developer, while GamingOnLinux tags the incident to both Kingdom Come: Deliverance and Kingdom Come: Deliverance II. Twisted Voxel describes Warhorse as a Prague-based studio known for historically grounded role-playing games set in early 15th-century Bohemia.
That context matters because a studio like Warhorse depends on interconnected production systems. An RPG of this kind is built across quest design, scripting, world data, localization, animation, cinematic work, QA databases, build distribution, partner communication, and patch planning. Warhorse has not said any of those areas were affected. The confirmed fact is broader and less specific: unauthorized access to company systems and company data.
The production risk, therefore, is a question rather than a conclusion. Security teams often need to isolate systems, audit access, rotate credentials, verify backups, and determine whether development environments can be trusted. None of the supplied sources report a delay, a service shutdown, a patch disruption, or a change to any Kingdom Come release plan. Until Warhorse says otherwise, any claim that the cyberattack has affected content timing or game availability would be speculation.
Warhorse is staying quiet while investigators define the breach
Warhorse has also made clear that it is not in a normal media cycle. According to the official statement quoted by GamingOnLinux and GamesIndustry.biz, the studio is not conducting interviews or providing additional comments while the investigation continues. That limits what can be responsibly reported, but it also helps explain why the public statement is careful and limited.
A company dealing with unauthorized access has competing obligations. It needs to secure systems before giving attackers useful information. It may need to coordinate with law enforcement or regulators. It may need to notify affected employees, partners, or users depending on what the investigation finds. Warhorse’s statement says it is coordinating with relevant authorities, but it does not name those authorities or describe any notification process.
For readers tracking the Warhorse systems affected by the incident, the next meaningful update would need to answer category-level questions. Which systems were accessed? What kinds of company data were involved? Was any personal data included? Were employees, contractors, partners, or players affected? Was any game material accessed? Did attackers exfiltrate data, or was access detected before that happened? Warhorse has not provided those answers yet.
The wider industry context makes the silence feel heavier
GamesIndustry.biz places the Warhorse incident alongside other recent industry security stories, including Capcom’s data breach affecting over 11.7 million online accounts and Rockstar-related breaches and leaks. GamingOnLinux also noted the Warhorse incident shortly after reporting a separate security incident involving Luanti, formerly Minetest, ContentDB. These comparisons do not prove a connection between incidents, and none is alleged in the supplied material.
They do show why players and developers pay close attention when a studio confirms unauthorized access. Game companies hold a mix of operational, creative, commercial, and personal data. For an RPG developer, unreleased builds or internal tools can become part of the community conversation even when players mainly want to know whether their own information is safe. Leaks can also distort expectations around unfinished work, especially in systems-heavy games where quests, balance, performance, and progression often change late in development.
For now, the most responsible reading is restrained. The Warhorse Studios cyberattack is confirmed. Unauthorized access to company systems and company data is confirmed. The incident is serious by the CEO’s own description. The unanswered questions are still the story: which data, whose data, which systems, what operational impact, and when Warhorse can safely provide a fuller account.