Minecraft Bedrock Edition had a security vulnerability that let malicious resource packs execute unauthorized code within the game's interface system. Mojang patched the issue with a hotfix in version 26.65, released on November 16, 2026, but did so without any statement explaining the scale of the threat. According to Tech Times, the hole was first exposed by add-on developer 8Crafter on Reddit, and the issue affected Bedrock versions from 26.52 to 26.63.
How the resource pack exploit worked
The problem involved a file named "content.zipe," which could be hidden inside a resource pack. This file could gain access to Ore UI, the TypeScript and React based framework responsible for Bedrock Edition's menus and interface. As a result, malicious code could run with the same permission level as the game's interface system, without triggering standard security alerts.
Most worrying of all, an infected resource pack could reach a player automatically the moment they connected to a server. There was no need for manual installation or downloading anything from a suspicious site: simply joining a specially crafted server was enough for the Bedrock client to download and run the harmful pack.
What players were at risk of
According to Tech Times, a malicious pack could, among other things, delete a player's saved worlds, hijack their account, or modify their friends list. The outlet writes that "a malicious pack could quietly rewrite friend lists, route the player onto attacker-controlled servers to capture their IP address." On top of that, there was a risk of unauthorized posts in Realms Stories and coordinated, fake reports being filed against targeted accounts.
- Deletion of the player's saved worlds
- Account takeover and changes to the friends list
- Redirection to attacker-controlled servers to capture the player's IP address
- Unauthorized posts in Realms Stories
- Mass, fake reports filed against targeted accounts
On Windows PCs, things were even worse. Tech Times describes the exploit as going a step further, "converting what appeared to be a texture download into a live malware dropper": what looked on the surface like a simple texture download could, in practice, open arbitrary URIs and install external malware. Java Edition was not vulnerable to this issue, since it doesn't use Ore UI in this form.
Mojang and community response
Mojang released the patch on November 16, the same day the issue started gaining wide media attention. However, the company didn't publish any official statement, patch notes entry, or CVE number confirming the scale and mechanics of the hole: Tech Times itself notes that "no official statement, patch note entry, or CVE designation has confirmed this." For players using the Bedrock Edition download, this means the safest way to protect yourself is to update to version 26.65 or newer, even though Mojang hasn't explicitly described what the patch protects against.
The community didn't wait for Mojang's explanation and reacted on its own. The creator of the Better Bedrock pack, known as AxmBro, published a batch script that lets players scan their Minecraft installation for the content.zipe file, including inside .mcaddon and .mcworld archives. This matters for players who installed resource packs from unknown sources before November 16, since an infected file could remain saved locally even after the game client was updated.
What this means for Polish players
This mainly concerns people playing on Bedrock Edition servers from unknown or unverified sources, where resource packs are sometimes forced automatically on connection. Before joining a new, unknown server on console, phone, or Windows, it's worth checking whether your game client is running version 26.65 or higher, and treating minecraft.pl's server list as a safer starting point than random IP addresses found online. Players using add-ons and packs from third-party sites should also check out the Minecraft wiki to remind themselves how to safely install community-made content.
For now, it's unclear whether Mojang plans to publish a broader explanation of the incident or an official changelog entry regarding version 26.65. Until such a statement appears, the only confirmed source of information about the exploit's mechanics remains the community investigation sparked by 8Crafter's report.