How nightmare-eclipse/yellowkey works
1. This repository does not contain source code or buildable application logic. It is a small on-disk payload composed of a prebuilt FsTx directory tree plus a README describing how that payload is used to trigger a Windows recovery-time BitLocker bypass.
2. The top-level artifact is FsTx/95F62703B343F111A92A005056975458/, which looks like a fixed, target-specific identifier or volume-scoped directory. That directory is the root of the crafted filesystem state intended to be copied verbatim.
3. Inside it are two main state areas: FsTxLogs/ and FsTxTemp/. This suggests the payload relies on Windows filesystem transaction / recovery metadata rather than executable binaries. The repo is therefore an artifact repository, not a software service architecture.
4. FsTxLogs/ contains paired log files and container files:
- FsTxLog.blf and FsTxKtmLog.blf
- FsTxLogContainer...
- FsTxKtmLogContainer...
These names strongly indicate Windows transaction/log replay structures used by the Kernel Transaction Manager and related filesystem components. The container files appear to be the bulk data backing those logs.
5. FsTxTemp/98F62703B343F111A92A005056975458 is the second state segment. Its presence implies the payload depends on a specific temporary working set or staged transaction state, likely to be consumed by Windows during mount, recovery, or repair processing.
6. The README defines the operational boundary: the payload is copied into System Volume Information\FsTx on a USB stick or similar writable volume. That external medium is the only distribution mechanism in the repo’s architecture; there is no network, service, or runtime component here.
7. The attack path crosses three boundaries:
- attacker-controlled removable storage,
- Windows Recovery Environment / WinRE,
- the BitLocker-protected target volume.
The exploit is triggered during WinRE startup, after a reboot flow initiated from the lock screen or recovery path.
8. The README indicates the vulnerable behavior is specific to Windows 11 and Server 2022/2025, and that it occurs in a WinRE component mirrored by a similar component in normal Windows installations. That implies the repo is targeting an environment-specific code path, not a generic disk format weakness.
9. Architecturally, this repo’s “data flow” is simple: attacker prepares the FsTx directory tree, places it on removable media, Windows WinRE reads and processes the filesystem metadata, and the result is an unrestricted shell over the protected volume. The repo itself contains only the trigger state, not the exploit logic.
10. For an architecture diagram, the main boxes should be: “crafted FsTx filesystem artifact,” “removable USB / EFI-staged storage,” “WinRE filesystem/transaction handling,” and “BitLocker-protected system volume.” The critical arrow is the WinRE component consuming the crafted FsTx state and transitioning into an unlocked shell context.
Main entry points: 95F62703B343F111A92A005056975458 FsTx tree · FsTxLogs FsTxLogs · FsTxTemp FsTxTemp · README.md README
Components 9
Crafted payload
Prebuilt FsTx directory tree copied onto removable media.
- README · Operational notes describing how the payload is staged and triggered.
README.md - FsTx tree · Top-level crafted filesystem state used as the payload root.
FsTx/95F62703B343F111A92A005056975458 - FsTxLogs · Transaction log area containing BLF metadata and container files.
FsTx/95F62703B343F111A92A005056975458/FsTxLogs - FsTxTemp · Staged temporary state segment used by the crafted recovery flow.
FsTx/95F62703B343F111A92A005056975458/FsTxTemp
Windows recovery path
System components that consume the crafted filesystem state during recovery.
- USB storage · Attacker-controlled removable volume that carries the crafted FsTx tree.
- WinRE · Windows Recovery Environment path that reads and replays the filesystem state.
- FsTx handler · Filesystem transaction and recovery metadata processing path in WinRE.
Protected volume
BitLocker-protected system volume reached after the recovery-time transition.
- System volume · BitLocker-protected target volume exposed after the recovery-time bypass.
- Unlocked shell · Resulting shell or recovery context with access to the protected volume.
Connections 10
- README → USB storage: staging instructions · The README defines copying the payload onto external writable storage.
- FsTx tree → FsTxLogs: contains · The crafted root includes the transaction log subtree.
- FsTx tree → FsTxTemp: contains · The crafted root includes the staged temp subtree.
- FsTxLogs → FsTx handler: metadata consumed · BLF files and log containers are consumed as recovery metadata.
- FsTxTemp → FsTx handler: staged state · Temporary state contributes to the replayed filesystem transaction view.
- USB storage → WinRE: boot path · The payload is mounted and reached during the recovery boot flow.
- WinRE → FsTx handler: processes · WinRE reads and processes the crafted FsTx structures.
- FsTx handler → System volume: boundary crossing · The replayed state influences access to the protected volume.
- System volume → Unlocked shell: unlocked access · The end state is an unrestricted shell or equivalent access context.
- WinRE → Unlocked shell: transitions to · The recovery component transitions into the post-bypass execution context.