This is what happens when the source code isnt open to review.
Microsoft has been committing class war against computer users since the 90's and they get all butt hurt as soon as someone holds their code to the flame.
This is a most excellent place for technology news and articles.
This is what happens when the source code isnt open to review.
Microsoft has been committing class war against computer users since the 90's and they get all butt hurt as soon as someone holds their code to the flame.
If she's going for maximum damage, I am surprised this person doesn't just announce when she's found a big exploit, and then just sell it to up to 10 people, and then announce in very vague terms what the exploits are. (Like, "just sold exploit for windows defender" or "just sold way to hack into bitlocker").
It seems like the vagueness of such things would make corporations more worried about being hacked and Microsoft could only guess as to what specific code was hacked, costing them greater resources.
Yes, it would be illegal, and therefore I hope she doesn't do that and recommend against it. But I am just surprised, given the level of anger, that she has been approaching things in a way that is so easy to patch.
Is her approach more damaging the way she's actually doing it?
What even is the headline
That was my thought, what a absolute mess of a 'sentence'.
Microsoft closed the case after the reporter refused to submit a video of the exploit
They don't have any actual fucking security experts there, so they require video proof that ape will understand.
Posting zero day exploits on github is a shit move. But Microsoft should be happy that this guy posted it on github rather than selling it on the black market.
Banning his guthub account won't make zero day vulnerabilities go away ffs.
You can well imagine that this reaction will fall on fruitful ground that some security experts will think twice about sending it to M$ or better selling it on the dark web, especially zero day exploits! Hell, boy, Microsoft does not seem to know with whom they are messing with.
I am so calling it 'guthub' from now on.
git gut(hub)
😅
This is extremely unfair to MicroSlop.
Didn't Google also recently used their stupid AI to find exploits in FFMPEG and then blackmailed them to fix it before deadline or they will release them to the public? If banning a dev for such "act" is right, then banning the company should also be right. Ban all of them.
The "vulnerability" in ffmpeg was only for an addon, which required a separate download by the user, which was only for a cinematic which was only in the game Star wars xwing vs tie fighter from the 90s, which would only occur at exactly 17s into the fmv.
There was a protocol for reporting security vulnerabilities. Of course some companies don't follow the protocol when vulnerabilities are reported to them, but that's their problem.
You report the problem and then you wait 1 month, if the company still hasn't fixed the issue by then, then you publicly announce it.
Unless it is an open source piece of software, any vulnerability I find will be publicly posted while I remove all software using it from all my devices and infrastructure.
The thing is if you want to continue working in the industry you have to give people the benefit of the doubt and give them time to fix the issue. If you don't do that you're very quickly find yourself to be out of a job no one wants to lose cannon, is bad for business.
Uniformed other than a few snippets from the blog but the researcher doesn't seem to be in a good place mentally. Understandable if what they claim is true, making them unreliable if it isn't.
Not victim blaming, but things aren't automatically true because they are anti Ms.
From what I've heard, the POC worked.
I think it's less being uncertain about the vulnerability and more about being uncertain about all the other drama surrounding it.
This Dormann fellow paints a believable picture of MSRC as an organization ruined by mismanagement and left incompetent and dysfunctional. A very banal scenario of failure that is familiar to anyone with experience with big businesses. Eclipse seems to see a more malicious intent and assumes that MSRC had it out for Eclipse personally from the onset for... some reason.
Eclipse may have found real stuff, but the communication style is a bit unhinged so it's hard to evaluate the surrounding drama. This unhinged communication style combined with a bureaucratic MSRC could lead to them not being able to understand Eclipse's attempt to explain.
The question is whether Eclipse was unhinged from the onset or understandably driven off the deep end by malicious treatment by MSRC. Both scenarios are believable, hence the sensible take away that we have one side of the story and while we should recognize that, we must also consider that an alternate scenario played out.
“Hey, let’s piss off the security expert who’s really good at finding flaws in our products. There’s literally no downside.”
"Oh, the one who just published two exploits on our product, after we fucked them over during the responsible disclosure process? Great idea! What are the chances they'll find another one, right?
I feel that companies like Microsoft have forgotten that bug bounties and ethical reporting are the compromise where they agree to pay a fair amount for the bugs and are given time to fix them and the security researcher forgoes the 10x price they could get on the black market.
Given the rise in mercenary hacking/spyware corporations, the bug researchers could probably get way more money through those alternate, and still legal, channels.
So I hear.
I'm surprised admins found a window large enough when github wasn't down to ban the researcher.
Is this the bitlocker backdoor? That's not an exploit / zeroday
Thats making a backdoor be known.
Well the thing is it’s now been zero days since they had to write a new backdoor.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Okay,
So let me get this straight, when I actively asked you to communicate with me, you refused, humiliated me and made sure to insult me in front of people.
You defame me in public with your CVE-2026-45585 advisory even though you literally deleted the Microsoft account I used to report bugs to you with and I got zero pennies from doing so and I still happily did like an idiot.
Now you take the courtesy to flag my github account and wipe it out of the public, just like that ? You are proving to everyone that you actively escalating this conflict but I'm done begging you.
I might sound like crazy idiot who is whinning around but I have proof for every single word I said, I just can't release it yet. Why ? Microsoft still has chains in my hands, it's been like this for years and I just can't stay silent anymore. I hope I can release the documents soon.
Mark this date July 14th, I will make sure your bones are shattered that day. Nothing will be released this June (or maybe I will release smtg, depending on circumstances).
Also,
CVE-2026-45498 is UnDefend
CVE-2026-41091 is RedSun
New GitLab account,
https://gitlab.com/nightmare-eclipse
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQRJTvAf/AWVhAKEeb7FFoRCS0/SbAUCahGg+gAKCRDFFoRCS0/S
bBMIAPsEczivsL71pbJizJHHlNNOf9guPAFFshJhhkwrDrwZ5wD/Vz6Z+d6vSvhQ
uVrEh4lPM84Q8+J56RLa50Zp46QLkAY=
=8wON
-----END PGP SIGNATURE-----
https://deadeclipse666.blogspot.com/
Their account on GitLab is already blocked https://gitlab.com/nightmare-eclipse

What's the context here?
Can't wait for the drama to escalate. Maybe he sells these on black market for millions? Who knows. Banning his account is like pouring salt on the wound.
This is a cartoonish level of evil by Microsoft blud
I mean, the cartoonish evil was making the backdoor in the first place. This is just inept.
Man, Microsoft just keeps footgunning this one.
Every new exploit, they clearly have a meeting and convince themselves "that's gotta be the last of it, right?"
So the next day-after-patch-tuesday rolls around and lo and behold, this guy drops some more nukes on their reputation as far as their most important customer demographic are concerned (corporate IT)
Given this genuinely does seem to stem from Microsoft mishandling this guy, why the fuck do they keep escalating
Microsoft has been mum on any details about these matters, so it's hard to tell if the situation is about an uncooperative researcher who doesn't follow standard disclosure rules or a company being difficult about security reports. Regardless, the move to ban Eclipse's GitHub account makes for poor optics, as it is being heavily criticized, and ultimately achieves nothing for security, since the code is out there anyway.
Classic Streisand effect. Just two years ago Satya Nadella publicly announced they're prioritizing security above all else, but now have nothing to say about these exploits and are trying to silence the researcher? Viewing from the sidelines, it did seem a bit reckless how Eclipse was dropping these as zero days, but Microsoft's actions speak louder than words and they probably didn't pay for the bounties.