Key Takeaways (TL;DR)
- The Incident: Validated Level 0 BootROM keys for the PlayStation 5 were published on December 31, 2025.
- The Severity: This is a hardware-level vulnerability. Sony cannot patch existing consoles via software updates.
- The Entry Point: Exploitation on Firmware 12.00 currently requires the game disc of Star Wars: Racer Revenge or a custom BD-J Burned Disc.
- The Impact: Allows for potential “Coldboot” Custom Firmware (CFW), advanced Linux support, and significant leaps in PC emulation (shadPS4).
- User Action: Users seeking to preserve jailbreak potential must disconnect from the internet immediately. Do not update system firmware.
As the world rang in the New Year, Sony PlayStation engineers were likely waking up to a nightmare. In the final hours of 2025, reports began flooding the internet that the PlayStation 5 ROM Keys—the deepest, most protected layer of the console’s security architecture—have been leaked.

This is not a kernel exploit that can be patched with a firmware update. This is the hardware root of trust. And it is out in the wild.
In this massive deep dive, we are breaking down exactly what happened, who is responsible, why this is considered “unpatchable,” and what this means for the future of the PS5, piracy, homebrew, and emulation.
The Leak: What Happened on New Year’s Eve 2025?
While most of the world was preparing champagne and fireworks, the underground console hacking scene was detonating a different kind of explosive.
Late on December 31, 2025, reputable figures in the PlayStation scene began discussing a massive data dump appearing on psdevwiki.com and various private Discord servers. The dump allegedly contained the Level 0 BootROM keys for the PlayStation 5.
For the uninitiated, the “BootROM” is the very first piece of code the PS5 processor executes when you press the power button. It lives on a read-only memory chip etched directly into the silicon. Its job is to verify that the next stage of the startup process is legitimate and signed by Sony.
If you have the keys to the BootROM, you effectively own the hardware. You can decrypt the bootloader. You can reverse-engineer the “Chain of Trust.” You can see exactly how the PS5 wakes up and decides what software is allowed to run.
The Source: @BrutalSam_, @Shadzey1, and the Deleted Tweets
The leak gained immediate traction when identified by prominent scene developers.
- @BrutalSam_: A known figure in the modding community, posted details regarding the keys. His post was rapidly taken down, citing a violation of X (formerly Twitter) rules, which often serves as a silent confirmation of the leak’s legitimacy. When platform holders’ issue DMCA takedowns or TOS violations on specific hex strings, it usually means those strings are real proprietary data.
- @Shadzey1: Another developer confirmed the development, adding credibility to the chaos.
Currently, the specific alphanumeric strings of the keys are spreading across encrypted messaging apps and forums like 4chan and private specialized boards, despite efforts to scrub them from the clearnet.
Warning: We will not be publishing the actual keys in this article to comply with legal standards. However, their existence is now public knowledge in the tech world.
Technical Deep Dive: What Are ROM Keys?
To understand about the BootROM Keys, one must understand the boot sequence of the PS5’s AMD Secure Processor (PSP).
Modern consoles use a security concept called a “Chain of Trust.”

- Level 0 (BootROM): The processor executes read-only code hardwired into the silicon. It uses the Root Keys to verify the signature of the next stage.
- Level 1 (Bootloader): Loaded only if the BootROM validates its digital signature.
- Level 2 (Kernel/Hypervisor): The operating system loads.

The Failure Point
The leak exposes the keys used in Step 1. Because the BootROM code is immutable (Read-Only Memory), Sony cannot change the lock on existing consoles. With these keys, a malicious actor can sign a custom Bootloader. The hardware will validate this custom code as “legitimate” because the cryptographic signature matches, granting Ring 0 / Bare Metal access.
The Cryptographic Significance
The PS5 uses an AMD-based custom APU. The ROM keys are used to decrypt and verify the initial stages of this chain. Until now, hackers have mostly been attacking the Kernel (Level 2) or the Webkit browser (Userland). These are “software” exploits. Sony fixes them by releasing a System Software Update (e.g., Firmware 12.00).
The ROM Keys change everything. With these keys, hackers can decrypt the Level 1 Bootloader. They can study exactly how the PS5 security works at the bare metal level. It removes the “black box” aspect of the console’s security. It is akin to losing the master key to the bank vault, rather than just knowing how to pick the lock on the front door.
The Entry Vector: “Star Wars: Racer Revenge”
While the ROM keys provide the permissions to run code, hackers still need a door to enter the system. For consoles running Firmware 12.00 and below, two primary entry vectors have been identified:
Researchers have identified a critical vulnerability within the PS2 emulator wrapper used by Star Wars: Racer Revenge. By loading a specifically crafted save file (exploiting a buffer overflow in the game’s racer selection screen), the exploit escapes the emulator’s sandbox. Combined with the leaked ROM keys, this grants system-wide access. This vector is particularly potent because Star Wars: Racer Revenge is a legacy title often available cheaply or via legacy game libraries.

Important! If you own a copy of Star Wars: Racer Revenge, do not delete or sell it. It has effectively become the “boot disc” for the first wave of PS5 custom firmware on the latest firmware.
Why Sony Cannot Patch This (The “Hardware” Problem)
This is the part that investors and executives at Sony Interactive Entertainment are sweating over.
ROM means Read-Only Memory. The code and keys in the BootROM are physically etched into the silicon of the APU during manufacturing. Sony cannot change these keys on consoles that are already in your living room.
- Scenario A (Firmware Update): Sony releases an update that changes the keys used by the software.
- The hardware BootROM still expects the old keys to verify the bootloader. If Sony changes the lock, the key in the hardware won’t fit, and the console won’t turn on. They are stuck with these keys for every PS5 currently in existence (Standard, Digital, and the recently released models).
- Scenario B (Hardware Revision): The only fix.
- Sony must manufacture new APUs with new ROM keys. This means a “v2” motherboard. Any PS5 bought before this future revision is permanently vulnerable to whatever exploits stem from this leak.
This is exactly what happened with the Nintendo Switch (fusee-gelee) and the early PS3. The “unpatched” units became gold dust, selling for premiums on eBay because they were permanently hackable.

The History of Console Security: From PS3 to PS5
History repeats itself, and the PlayStation lineage is no stranger to catastrophic key leaks.
The PS3 (2010-2011)
The famous fail0verflow hack. Sony made a cryptographic mistake (using the same random number for signing), allowing hackers to calculate the private signing keys. This blew the PS3 wide open, allowing Custom Firmware (CFW) on all devices. It was a disaster for Sony, leading to rampant piracy and cheating in Call of Duty and GTA.
The PS4 (2013-2025)
Sony learned. The PS4 security was tighter. While we have Kernel Exploits (GoldHEN), we never got a full BootROM leak that compromised every device permanently. The PS4 scene relies on finding older firmware consoles (9.00, 11.00) to run exploits.
The PS5 Era (2020-2025)
Until yesterday, the PS5 was holding up relatively well. We had the IPv6 Kernel Exploit and the BD-J (Blu-ray) exploits, but these were patchable. This new leak essentially drags the PS5 back to the “PS3 era” of vulnerability. It implies that the “Root of Trust” is no longer trustworthy.
The Impact on Jailbreaks & Homebrew
What does this mean for the average user?
1. Acceleration of Custom Firmware (CFW): With the ability to decrypt the bootloader, developers can potentially create a Custom Bootloader. This is the holy grail. It would allow a PS5 to boot directly into a modified Operating System (like Linux or a modded PlayStation OS) without needing to run an unstable exploit every time you turn the console on.
2. Permanent “Coldboot” Hacks: Current PS5 hacks are “tethered” or semi-tethered (you have to re-apply them after a reboot). A ROM-key based exploit could lead to a “Coldboot” hack, where the console is jailbroken the moment you press the power button, just like a modded PS3.
3. Linux Support: PS5 Linux support is already decent, but this will make it flawless. Driver developers can see exactly how the hardware initializes, leading to better 3D acceleration and performance in Linux gaming on PS5.
The Piracy Question: Is It Open Season?
Disclaimer: We do not condone piracy. This analysis is for educational and news purposes only.
The inevitable question: “Can I play free games now?”
Short Answer: Not today, but likely soon.
Long Answer: Just having the ROM keys doesn’t instantly mean you can run pirated games. The PS5 OS still has layers of “DRM” (Digital Rights Management) and checks inside the kernel. However, the ROM keys give hackers the map to find the remaining checks.
It removes the biggest hurdle. Usually, hackers spend years just trying to “see” the code. Now they can see it. It is highly probable that we will see more sophisticated game backups and loaders appearing in 2026. This leak significantly shortens the timeline for mass piracy.
The Emulation Scene: A Turbo Boost for shadPS4?
The most constructive outcome of this leak is the acceleration of software preservation and emulation.

Emulators like shadPS4 and Kyty have historically relied on High-Level Emulation (HLE)—essentially guessing how the PS5 hardware processes instructions. With decrypted bootloaders, developers can now perform Low-Level Emulation (LLE).
With the decrypted BootROM and keys:
- GPU Initialization: Developers can read exactly how the PS5 initializes its RDNA 2 GPU.
- Proprietary APIs: Encrypted libraries for 3D audio and compression (Kraken) can now be decrypted and reverse-engineered.
We might see playable Bloodborne (at 60FPS) or Demon’s Souls Remake on PC much sooner than expected thanks to this leak.
Community Reaction: NeoGAF, Reddit, and Discord
The internet is reacting exactly as you’d expect: Chaos.
- NeoGAF Thread #1691813: The thread has exploded with over 5,000 replies in 24 hours. Users are debating the ethics of the leak vs. the preservation aspect.
- Reddit (r/PS5homebrew): The top post is simply “IT HAPPENED.” Users are advising others to STOP UPDATING their consoles immediately.
- X (Twitter): Memes about “Sony HQ on fire” are trending. Security researchers are pouring over the
psdevwikiupdates.
The Golden Rule of the Scene: If you want to hack your console, DO NOT UPDATE. Disconnect your PS5 from the internet immediately. If Sony pushes an update (e.g., Firmware 13.00) in panic, it won’t fix the ROM keys, but it might obfuscate other entry points needed to use them.
Sony’s Potential Response: PS5 Super Slim / Pro V2?
What can Sony do? They are in a corner.
- Legal Action: Expect subpoenas to Twitter, Discord, and ISPs to hunt down the leakers.
- Ban Waves: Sony may implement aggressive checks on PSN. If a console is detected running with a modified bootloader, expect an instant hardware ban (Console ID ban).
- Hardware Revision: We predict Sony will quietly rush a “Revision 3” or “Super Slim” model into production for late 2026. This model will have new keys burnt into the silicon. This will create a market dynamic where “Pre-2026 PS5s” are more valuable than newer ones.
The End of an Era
The leak of the PS5 ROM keys on December 31, 2025, marks the end of the “Secure Era” for the PlayStation 5. While the console isn’t “dead”—it will continue to sell millions and play great games—its security integrity is shattered.
For the modding community, this is a Golden Age. For Sony, it’s a crisis management exercise. For the gamer, it’s a waiting game to see what software emerges from this Pandora’s Box.
One thing is certain: The PlayStation 5 you own today is not the same console it was yesterday. It is now an open book.
Frequently Asked Questions (FAQs)
Does this mean I can jailbreak my PS5 on the latest firmware?
Not instantly. The keys allow developers to find exploits easier, but you still need an entry point (like a kernel exploit) to use them. However, the chances of a jailbreak for latest firmwares have skyrocketed.
Can Sony ban me?
Yes. If you use custom firmware or modified files and connect to the PlayStation Network (PSN), Sony can detect the anomaly and ban your account and console permanently.
Should I buy a PS5 now?
If you are interested in modding, YES. Buy one now before Sony releases a hardware revision that fixes this vulnerability. Look for “Old Stock” or used consoles from 2020-2025.
Is this related to the PS5 Pro?
The PS5 Pro likely shares the same ROM architecture as the base PS5. If so, the Pro is also compromised. If the Pro uses a newer key set (unlikely for compatibility reasons), it might be safe.
What do I do with my PS5 right now?
Go to Settings > System > System Software > System Software Update and Settings > Turn OFF “Download Update Files Automatically” and “Install Update Files Automatically”. Disconnect from the internet if you are serious about waiting for a hack.








