The YellowKey BitLocker Bypass: How the Attack Works and How to Stay Protected
Introduction
In early 2025, a researcher known as Nightmare-Eclipse released a proof-of-concept exploit called YellowKey that targets Microsoft’s BitLocker full-disk encryption on default Windows 11 deployments. The exploit is particularly dangerous because it can reliably bypass BitLocker’s protection—even when the decryption key is stored in a Trusted Platform Module (TPM)—provided the attacker has physical access to the computer. For organizations that rely on BitLocker as a mandatory security measure, this vulnerability poses a serious risk. This guide breaks down the steps an attacker would take to exploit this weakness, explains the underlying mechanism, and offers practical tips to defend against it.

What You Need
To understand or simulate the YellowKey attack (for educational purposes only), you should have the following:
- A Windows 11 system with default BitLocker settings (using TPM-only or TPM+PIN authentication)
- Physical access to the computer (the exploit requires direct interaction with the hardware)
- A bootable USB drive containing the YellowKey payload (available from the researcher’s GitHub repository)
- Basic knowledge of UEFI/BIOS boot processes and TPM architecture
- An isolated test environment (do not run this on production machines)
The Step-by-Step Attack Process
The following steps outline how an attacker with physical access would execute the YellowKey exploit. Each step is explained in detail.
Step 1: Gain Physical Access to the Target Computer
The most critical prerequisite is physical proximity. The attacker must be able to touch the machine, power it on, and interact with the boot process. This could happen if a laptop is left unattended in a public place, stolen, or obtained through an insider threat. Without physical access, the exploit cannot be launched.
Step 2: Identify the BitLocker Configuration
The attacker checks whether the system uses BitLocker with default TPM-only protection. This is common on many corporate Windows 11 deployments. The TPM stores the cryptographic key that decrypts the drive automatically during boot. YellowKey specifically targets this setup; it does not work if the user has set a pre-boot PIN or a startup key, as those require additional authentication before the TPM releases the key.
The attacker can quickly verify the configuration by booting the system once and observing the boot screen. If no PIN or key prompt appears, the system is likely using TPM-only protection.
Step 3: Prepare the YellowKey Bootable USB
Before the attack, the attacker crafts a bootable USB drive with the YellowKey exploit. The payload is designed to trick the TPM into releasing the decryption key without proper authorization. The attacker downloads the latest release from Nightmare-Eclipse’s GitHub repository and writes it to a USB drive using tools like Rufus or dd. The USB must be formatted as a bootable UEFI device.
Step 4: Boot from the USB Drive
With the USB inserted, the attacker restarts the target computer and enters the boot menu (usually by pressing F2, F12, or Del during startup). They select the USB device as the primary boot option. The system then loads the YellowKey environment instead of the normal Windows boot manager.
Step 5: Execute the YellowKey Exploit
Once the YellowKey environment loads, the attacker runs the exploit. The tool exploits a weakness in how Windows 11 configures the TPM for default BitLocker deployments. Specifically, it takes advantage of the fact that the TPM is set to release the decryption key automatically when it detects the same hardware state (including PCR registers) as during normal boot. YellowKey manipulates the boot process to replay a valid set of PCR measurements without the operating system’s security checks. This causes the TPM to hand over the full-volume encryption key.

The exploit does not require any authentication or bypass of additional PINs—it only works because the TPM trusts the hardware state presented by the YellowKey boot loader.
Step 6: Access the Decrypted Drive
After the TPM releases the key, the exploit mounts the decrypted volume. The attacker can now browse the contents of the system drive as if it were an unlocked external disk. All files, folders, passwords, and sensitive data become readable. The attacker may copy data to an external device or install malware. Importantly, the decryption is performed in memory and does not alter the original encryption on disk, leaving no obvious traces.
Tips for Protection and Mitigation
While YellowKey is a serious vulnerability, you can take steps to reduce the risk:
- Use a pre-boot PIN or startup key. Microsoft recommends adding a PIN or requiring a USB startup key for BitLocker. Even a simple PIN prevents the TPM from releasing the key without human interaction. To enable this, open Manage BitLocker and select “Require a PIN at startup.”
- Enable TPM with enhanced protections. Some modern systems support TPM 2.0 with additional security features like brute-force resistance. Ensure your firmware is up to date.
- Apply the latest Windows security patches. Microsoft may release a fix for this vulnerability in future updates. Keep Windows Update active.
- Practice physical security. Never leave your device unattended in public. Use laptop locks when in shared offices, and report stolen devices immediately.
- Monitor boot events. Enable Secure Boot and configure audit logs to detect unauthorized boot devices. Some enterprise security tools can alert on unexpected boot sequences.
- Test your defenses. If you are an IT administrator, simulate the attack in a controlled lab to understand its impact and verify that mitigations work.
Remember, YellowKey requires physical access—so the strongest defense is keeping your device out of an attacker’s hands. Combine that with a strong BitLocker PIN, and you effectively neutralize this exploit.
Related Articles
- Canvas Cyberattack During Finals: Key Questions Answered
- Cloudflare’s Proactive Defense Against the Copy Fail Linux Kernel Vulnerability
- Comprehensive Guide to Securing Your npm Supply Chain: Threats and Defenses
- Supply Chain Breach: How AI EDR Thwarted a Major Watering Hole Attack on CPU-Z
- How a Brazilian DDoS Protection Firm Was Used to Launch Attacks on Its Own Customers
- Critical 'Copy Fail' Bug Lets Unprivileged Users Gain Root on Nearly All Modern Linux Systems
- Canvas Cyberattack Highlights Persistent Education Cybersecurity Gaps
- How to Protect Your Exim MTA from the BDAT Vulnerability (CVE-2026-45185)