milliways-infosec/YellowKey
5
0
Fork 0
mirror of https://github.com/Nightmare-Eclipse/YellowKey.git synced 2026-05-16 10:40:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
YellowKey Bitlocker Bypass Vulnerability mirror
4 commits 1 branch 0 tags 72 KiB
Find a file
dabeersboys 4216ed9e2b
Added PS1 file 
This file will create the USB for Yellow Key
2026-05-14 14:55:08 -06:00
FsTx/95F62703B343F111A92A005056975458 Add files via upload 2026-05-12 19:23:00 +02:00
LICENSE Initial commit 2026-05-12 17:54:59 +02:00
README.md Update README.md 2026-05-12 19:27:16 +02:00
shell.png Add files via upload 2026-05-12 19:23:00 +02:00
USB_Build.ps1 Added PS1 file 2026-05-14 14:55:08 -06:00

README.md

YellowKey

YellowKey Bitlocker Bypass Vulnerability

Been a while since I saw a bitlocker bypass around, my turn.

This is one of the most insane discoveries I ever found, almost feels like backdoor but what do you know, maybe I'm just insane.

How to reproduce :

  1. Copy the FsTx folder to "YourUSBStick:\System Volume Information\FsTx" as is and make sure to use a filesystem that's compatible with Windows (NTFS is preferable but I think FAT32/exFAT should work as well). Funny thing is, the vulnerability is extremely convenient, you don't even need to plug an external storage device, you can just pull out the disk, copy the files in the EFI partition, put it back and it will still work. That's how bad it is.
  2. Plug the USB stick in your target windows computer with bitlocker protection turned on.
  3. Reboot to Windows Recovery Environment Agent (you can do that by holding SHIFT and clicking on the restart button using your mouse)
  4. Once you click on the restart button, lift your finger off the SHIFT key and hold CRTL and do NOT lift your finger off it.
  5. If you did everything properly, a shell will spawn with unrestricted access to the bitlocker protected volume.
shell

Now why would I say this is a backdoor ? The component that is responsible for this bug is not present anywhere (even in the internet) except inside WinRE image and what makes it raise suspicions is the fact that the exact same component is also present with the exact same name in a normal windows installation but without the functionalities that trigger the bitlocker bypass issue. Why ? I just can't come up with an explanation beside the fact that this was intentional. Also for whatever reason, only windows 11 (+Server 2022/2025) are affect, windows 10 is not.

A huge thanks to MORSE, MSTIC and Microsoft GHOST for making this public disclosure possible ;)