Warhorse Studios, the Czech team behind Kingdom Come: Deliverance, has been hit by a cyberattack. The studio’s public statement was short: it’s working with cybersecurity specialists to secure its systems and “understand the full extent of what happened.” Push Square reports that Warhorse has confirmed unauthorized access to both systems and data. Nobody outside the studio knows yet what was taken, and as of reporting there’s no sign of anything leaking.

CEO Martin Frývaldský was more direct in comments to Czech outlet CC.cz, calling it “a serious incident for Warhorse Studios and for everyone affected.” He listed the priorities as securing systems, finding the full scope of the breach, and protecting “our employees, partners, and our community.”

The order of that list matters, and I think it’s the right one.

The wrong thing to obsess over

The internet will immediately start asking what this means for unannounced games. Warhorse has a lot in the oven. There’s an open-world Middle-earth RPG based on The Lord of the Rings, a “new Kingdom Come adventure” that is almost certainly Kingdom Come: Deliverance 3, and a collaboration on a Kingdom Come film. That’s a tempting pile of secrets for anyone who wants screenshots or story details.

Those leaks would sting. They wouldn’t be the worst outcome. A spoiled reveal trailer is a marketing headache. Stolen payroll records, contracts, ID documents or internal emails are a problem for actual people who never signed up to be in a headline. When a studio says “data” was accessed, that’s the word I’d focus on.

If material does surface, players can do something useful by not spreading it. Every repost of leaked assets turns the attacker’s haul into currency.

The partner problem

The Lord of the Rings project complicates this in a way a purely in-house game wouldn’t. Licensed work means partners, and partners mean shared documents, approval chains and terms that a third party owns as much as Warhorse does. Frývaldský naming “partners” in his statement reads to me like a studio that knows its exposure goes beyond its own walls. That’s inference, but it’s the obvious place to look.

It’s also why I’m fine with the near-silence so far. The first statement went out at 11am GMT, and Eurogamer noted no update had followed. Some fans will read that as stonewalling. I’d rather a studio say nothing than guess publicly about scope and get it wrong, which forces a second, more embarrassing disclosure a week later.

That patience has a limit. If employee or partner data turns out to be part of the haul, those people should hear it from Warhorse quickly and specifically, not through a vague tweet thanking everyone for “standing with us.”

What we’re waiting on

Right now the confirmed facts fit in a paragraph: unauthorized access, systems and data involved, outside specialists brought in, no visible leak. Everything else is speculation, including whether this was ransomware, whether there’s a demand, and whether any game builds were touched.

The next statement from Warhorse should answer one question first: was employee data in the systems that were accessed?