The Windows OS Thread - Formerly THE OS for gamers and normies, now sadly ruined by Pajeets

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Oof

more 0days released.
Yellowkey allows access to bitlocker encrypted drives with just a simple usb drive
The anonymous security researcher who has already maliciously exposed three Windows zero-days this year has revealed two more, dropping them just after Microsoft's monthly Patch Tuesday update.

Nightmare-Eclipse, or Chaotic Eclipse, depending on which of their aliases you prefer, released details about YellowKey and GreenPlasma - respectively a BitLocker bypass and a privilege escalation flaw, handing SYSTEM access to attackers.

Experts speaking to The Register warned that both vulnerabilities present serious security concerns, especially since Nightmare-Eclipse released substantial technical information about exploiting them.


Nightmare-Eclipse described YellowKey as "one of the most insane discoveries I ever found." They provided the files, which have to be loaded onto a USB drive, and if the attacker completes the key sequence correctly, they are granted unrestricted shell access to a BitLocker-protected machine.


When it comes to claims like these, we usually exercise some caution, as this bug requires physical access to a Windows PC. However, seeing that BitLocker acts as Windows' last line of defense for stolen devices, bypassing the technology grants thieves the ability to access encrypted files.

Rik Ferguson, VP of security intelligence at Forescout, said: "If [the researcher's claim] holds up, a stolen laptop stops being a hardware problem and becomes a breach notification."

Despite the physical access requirement, Gavin Knapp, cyber threat intelligence principal lead at Bridewell, told The Register that YellowKey remains "a huge security problem for organizations using BitLocker."

Citing information shared in cyber threat intelligence circles, he added that YellowKey can be mitigated by implementing a BitLocker PIN and a BIOS password lock.

Nightmare-Eclipse hinted at YellowKey also acting as a backdoor, allegedly injected by Microsoft, although the people we spoke to said this was impossible to verify based on the information available.

The researcher also published partial exploit code for GreenPlasma, rather than a fully formed proof of concept exploit (PoC).

Ferguson noted attackers need to take the code provided by the researcher and figure out how to weaponize it themselves, which is no small task: in its current state it triggers a UAC consent prompt in default Windows configurations, meaning a silent exploit remains a work in progress.

Knapp warned that these kinds of privilege escalation flaws are often used by attackers after they gain an initial foothold in a victim's system.


"These elevation of privilege vulnerabilities are often weaponized during post-exploitation to enable threat actors to discover and harvest credentials and data, before moving laterally to other systems, prior to end goals such as data theft and/or ransomware deployment," he said.

MORE CONTEXT​

  • Doozy of a Patch Tuesday includes 30 critical Microsoft CVEs​

  • Microsoft's massive Patch Tuesday: It's raining bugs​

  • Researchers claim Windows Defender can be fooled into deleting databases​

  • Surrender as a service: Microsoft unlocks BitLocker for feds​

"Currently, there is no known mitigation for GreenPlasma. It will be important to patch when Microsoft addresses the issue."

Four, five… and more?​

YellowKey and GreenPlasma are the latest in a series of five Microsoft zero-day bugs the researcher has exposed this year.

When Nightmare-Eclipse released BlueHammer (CVE-2026-32201, 6.5) - patched by Microsoft in April - they were described as a disgruntled researcher who has since been rumored to be a former Microsoft employee.

According to their maiden blog post under the Chaotic Eclipse alias, the bug leak began after an alleged violation of trust.

"I never wanted to reopen a blog and a new GitHub account to drop code," they wrote. "But someone violated our agreement and left me homeless with nothing. They knew this will happen and they still stabbed me in the back anyways, this is their decision not mine."

In early April, the researcher leaked proof-of-concept code for Windows Defender exploits they called RedSun and UnDefend - another admin privilege escalation bug and denial-of-service flaw, respectively - as well as BlueHammer.


Both RedSun and UnDefend remain unfixed, and according to Huntress, the proof-of-concept code released was quickly picked up and abused in real-world attacks.

Ferguson described the exposure of YellowKey and GreenPlasma as the latest in an escalating, retaliatory campaign against Microsoft, and warned of more coming.

"Prior releases include BlueHammer and RedSun, both of which attracted serious community attention and real forks," he said.

"The same post linking yesterday's releases warns of another Patch Tuesday surprise and hints at future RCE disclosures. They claim to have a dead man's switch with more ready to go. This researcher has followed through on every prior threat." ®
 
Last edited:
I was considering installing win 11 on my new pc, with a local profile and as much as the bloat/ai disabled as possible. How bad is it going to be?
I waited years before upgrading to win 10, but it ended up being OK and not quite as bad as people said. Is it the same with 11?
 
I was considering installing win 11 on my new pc, with a local profile and as much as the bloat/ai disabled as possible. How bad is it going to be?
I waited years before upgrading to win 10, but it ended up being OK and not quite as bad as people said. Is it the same with 11?
Depends on the version and release channel. Home will probably always be bad.
 
I was considering installing win 11 on my new pc, with a local profile and as much as the bloat/ai disabled as possible. How bad is it going to be?
I waited years before upgrading to win 10, but it ended up being OK and not quite as bad as people said. Is it the same with 11?
It will be fine. The one thing you want to do almost immediately is to restore the normal right-click menu via command line, and of course move the Start menu to the left.

Here's my own starter folder, I don't know how to share it more permanently, it will be up for a few days:
---
EDIT: link already gone, hope you got it in time.
The activator in the folder was KMSpico, one of the oldest and simplest activators. The registry hacks to reactivate and clean up the normal context menu were mostly from elevenforum.
---
It bears repeating: do not fight one second more than necessary with the new context menu. I rest my case that it probably contributed to a big portion of the Windows 10 holdovers. It's like trying to work with a fire alarm blazing in your ear.
 
Last edited:
ℹ️ Tried out the latest Insider Preview — Canary Experimental for fun (Build 29591.1000), and let me tell you, you still can't do anything about the taskbar position. The K2 is a lie.
 
Last edited:
I was considering installing win 11 on my new pc, with a local profile and as much as the bloat/ai disabled as possible. How bad is it going to be?
I waited years before upgrading to win 10, but it ended up being OK and not quite as bad as people said. Is it the same with 11?
I'd recommend WinUtil for debloating and applying some saner preferences. I save my settings and reapply them with major Windows updates in case something has been reverted. Personally, I find Windows 11 perfectly fine to use after debloating. There's a lot of click bait tech articles about buggy Windows updates. More often than not these are 'preview' updates and you need to opt-in to receive them.

Here's my own starter folder, I don't know how to share it more permanently, it will be up for a few days:
....There's also an activator (disable Defender before you unzip it, run autopico.exe as admin).
This sounds sketchy.
 
There's a lot of click bait tech articles about buggy Windows updates. More often than not these are 'preview' updates and you need to opt-in to receive them.
Yes, those articles are almost always about unstable previews, without clearly mentioning it.
The Experimental build kept crashing my GPU driver, giving me a GSOD every time. I had 5 GSODs in 5 hours or so. IoT has never done that even once.
 
"I never wanted to reopen a blog and a new GitHub account to drop code," they wrote. "But someone violated our agreement and left me homeless with nothing. They knew this will happen and they still stabbed me in the back anyways, this is their decision not mine."
Is the madman telling us he went through a divorce?
Citing information shared in cyber threat intelligence circles, he added that YellowKey can be mitigated by implementing a BitLocker PIN and a BIOS password lock.
Not according to leaker. https://deadeclipse666.blogspot.com/2026/05/were-doing-silent-patches-now-huh-also.html?m=1 |
Archive
Second thing is, No, TPM+PIN does not help, the issue is still exploitable regardless, I asked myself this question, can it still work in a TPM+PIN environment ? Yes it does, I'm just not publishing the PoC, I think what's out there is already bad enough.

also lmao read this shit Link | Archive
In the off chance, you decide that you want to proceed with whatever funny ideas you have in your head. I'm recommending you that you do not do it, the dead man switch was active before this even started.

So if you decide to try me, everyone else will pay for it and this time it will be extremely. It will take you a lot of time to patch what will be published if the dead man switch is detonated.

Also if you somehow think I'm stupid, no, the dead man switch is insanely sophisticated it took me forever to deploy it and ensure it works properly before actually making it live and no it's not located at my place ;)

Don't say I did not warn you and again, I'm not bluffing. I deliver every promise I make.
 
Last edited:
Its really fucked that Windows used to have parity with Linux for supercomputers from throughput but now it can barely function for a basic desktop that its so obscenely bloated.
Never had parity. Ever. Their tools weren't really designed to scale to thousands of servers, and there was always a measurable per-core penalty for Windows HPC compared to Linux. MS-MPI was always behind in features compared to IBM Platform MPI (RIP) and Intel MPI. Open MPI is now the warty bug-filled hellproduct of choice.
 
I officially declare that Windows is no longer to be called Windows. It is to be called WinJeet, because of the pajeet CEO and the pajeet-like treatment the OS has been through.
 
Back
Top Bottom