Wednesday, 13 May 2026

We're doing silent patches now huh, also a quick note about YellowKey

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA512


I just noticed that Microsoft silently patched the RedSun vulnerability, no CVE, no nothing, just a silent patch. Not surprised they never admit their mistakes but considering it was under active exploitation, having zero advisory is insane.


Now regarding YellowKey, lots of you are wondering how does one even find such backdoor ?

I'll tell you how, it took me more time trying to get it to work than the amount of sleep I had in two years combined. No AI involved, no help in any shape or form. I could have made some insane cash selling this but no amount of money will stand between me and my determination against Microsoft.

Funny thing is, no one and I say again NO ONE has managed to figure out how YellowKey works, the real root cause is still not unknown by the general public. I think it will take a while even for MSRC to find the real root cause of the issue. I just never managed to understand why this vulnerability is sooo well hidden.

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.


I can't wait when I will be allowed to disclose the full story, I think people will find my crashout very reasonable and it definitely won't be a good look for Microsoft.


-----BEGIN PGP SIGNATURE-----


iHUEARYKAB0WIQRJTvAf/AWVhAKEeb7FFoRCS0/SbAUCagRfWwAKCRDFFoRCS0/S

bDlGAP42z1Tck5TFPhaUbrC7WHcDwzr/ajAPLfj2ttXKfph30gEAm0KIZyf874gb

WAAGxop9J4RtzHIcQG6iPd1UqmWxhwM=

=xXqu

-----END PGP SIGNATURE-----


Tuesday, 12 May 2026

Two more public disclosures, it will never stop

-----BEGIN PGP SIGNED MESSAGE-----

Hash: SHA512


Here are the links, yes, two vulnerabilities this time. Defender has been sparred because I know Microsoft will tighten the strings if I target one specific component too often. Don't ask how I know.


https://github.com/Nightmare-Eclipse/YellowKey

https://github.com/Nightmare-Eclipse/GreenPlasma


Microsoft has chosen to make this worst instead of resolving the situation like adults, they pulled every childish game possible. My patience is running out you're making everyone else paying for it.


I hope you at least attempt to resolve the situation responsibly, I'm not sure what type of reaction you expected from me when you threw more gas on the fire after bluehammer. The fire will go as long as you want, unless you extinguish it or until there nothing left to burn.


Your recent actions made me take the difficult decision to drag other companies into this, be prepared to answer questions.

Next patch tuesday will have a big surprise for you Microsoft. And remember, I never failed to deliver a promise.


-----BEGIN PGP SIGNATURE-----


iHUEARYKAB0WIQRJTvAf/AWVhAKEeb7FFoRCS0/SbAUCagNlvwAKCRDFFoRCS0/S

bCvjAQDVurDgXRdoE76+lSAsucc7bYTesGTQlhejiisdJD8oAwD+LK4GXV+apocq

pvzD/Ikz+6NV3PZD0TyDy7odM0KmKgI=

=5WrI

-----END PGP SIGNATURE-----


We're doing silent patches now huh, also a quick note about YellowKey

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I just noticed that Microsoft silently patched the RedSun vulnerability, no CVE, no nothing,...