It is widely acknowledged that material surfaced before March 2. The leak was linked to VK fan community admins who manage the audience. Previous coverage explored the conflict and its causes, but the arrival of a playable test version makes the story more compelling. Studio GSC Game World publicly accused Russian hackers of theft and pointed to the game’s creators for security gaps, suggesting the company did not adequately protect its files. The goal here is to clarify who is ultimately responsible for the leak and what it means for development of the project.
How it unfolded
Even though GSC Game World accused Russian hackers on social media, the timeline shows a more nuanced sequence of events.
Test builds—intended to debug and refine specific mechanics—were uploaded by developers to torrent trackers so remote workers could access essential files quickly. The 200 gigabyte archives were publicly accessible without privacy controls. Any passerby could locate and download them directly to a PC.
Files downloaded directly from GSC Game World servers
As a result, the test builds were found not by Russian hackers or Stalker fans, but by Western data miners. The 200 GB archive, even from the official developer server, appeared highly attractive. It was downloaded with little resistance, and inside was a raw build of STALKER 2. Data miners shared their discovery on a public imageboard, and information about the playable build spread globally from there.
Following the March release of the game’s design documents, the VKontakte Herald of the Same Stalker community drew intense scrutiny from followers of the STALKER universe. Through this group, the Russian-speaking community learned about the build and gained access to a download link. Many internet users concluded that the fan group administrators bore responsibility for the May 30 leak. Details about precisely how the link reached fans were not widely discussed.
Initially, the test version of STALKER 2 was encrypted and could take time to crack. To solve this, the group’s well-known coder joined in, beginning the process of parsing the leaked files.
Are there devoted STALKER fans among the readers?
Shortly after, on June 1, decryption keys circulated on the RedProjects Discord server. They did not require hacking or fresh coding. The necessary line of code appeared to exist in the test logs of the build itself. It became clear that none of the developers strictly guarded the test builds or protected their data.
Explanation of the person who found the decryption key
With the keys discovered, anyone could run the test build on a PC and extract the packed assets using a tool designed for the Unreal Engine 5 framework.
The studio’s management responded by posting a call to players on the project’s official Twitter page, blaming Russian-speaking hackers for malicious server activity that the company had faced for years. They urged fans to avoid early access and wait for the full release.
The VK administrators posted a response, arguing that the developers were being disingenuous and manipulating public perception. They insisted they were not hackers and merely informed the fan community about the possibility of downloading a test archive. They stated they were not linked to Russia and noted that their members were Ukrainian. The following quote is presented with minimal editing to preserve style and punctuation.
“In summary, even the leak of 15 GB of data and development in the game was done by Ukrainians and nothing more. In the recent build leak, GSC Game World themselves bear blame, mostly Ukrainians (Czechs). The Americans spotted the leak and we, Ukrainians too, subsequently shared it. And all this happened without hacks or exploiting vulnerabilities.”
From these viewpoints it becomes evident that no Russian-speaking hackers were involved, and no one intentionally hacked the developers’ servers.
After the test archive went online, opinions diverged about the incident:
- The leak was a PR maneuver for STALKER 2, a tactic the studio reportedly used during earlier projects like Shadow of Chernobyl. That explains the availability of multiple builds online, including previews from 2011 for STALKER 2.
- Some blamed a hacking incident with data miners or other unknown parties. It’s important to note that the March 15 design documents reached fans not through hacking but via open communication with the developers. Administrators and other members of the VK group did not hack in and they even banned members who called for a boycott. A separate article covers the design document leaks and the corresponding disagreements between group admins and GSC community managers.
- The third, most plausible reason is simple carelessness. The test rig ended up with users because an access point was not properly secured. Keys and decryption methods were not removed before sharing, and remote testing always carries risk.
Whether this leak will alter development remains unclear, but studio staff say work on the game continues as normal.
Who should bear responsibility for the leaked STALKER 2 test version?
In summary, the test build leak has deepened the divide between developers and Russian-speaking fans. Some fans face bans and regional sales restrictions while others contribute to distributing design documents and early builds.
The STALKER series stays in the spotlight thanks to a loyal community. Developers deserve a receptive audience, and fans should reduce hostility while showing understanding toward SGC staff facing a tough situation. The goal is for developers and fans to reach a shared understanding and end the obstruction between them.
Source: VG Times