home.social

#nightmareeclipse — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nightmareeclipse, aggregated by home.social.

fetched live
  1. On another news NightmareEclipse (the goat?) returned with a new PoC, after Microsoft failed to fully patch RoguePlanet (CVE-2026-50656), the current PoC only made for latest Windows 11 release, but they said that Windows 10 also still vulnerable. And yeah, it works even after the latest update

    github.com/MSNightmare/ShieldB

    #cybersecurity #infosec #zeroday #vulnerability #windows #nightmareEclipse

  2. Maybe a bit of an explanation why it does this:

    When a new user is logging on, Windows needs to load the users class hive. Since the user isn't logged on before logging on (tautology, I know), it can't be loaded in the context of the user. So it is loaded in the context of NT AUTHORITY\SYSTEM.

    LegacyHive abuses this.

    It messes with the Windows Object Manager and instead of the actual UsrClass.dat hive points at C:\randomGUID\UsrClass.dat. then it places an oplock on that file and starts an (interactive) logon for the user whose Object Manager path has been manipulated.
    This leads Windows to try to open the file, but it can't, because of the Oplock. So the process looks at the Object Manager namespace again, finds a symlink (also manipulated by LegacyHive) and loads that instead, attaching it as the class hive for the user it is trying to create an interactive session for.
    The load succeeds because, as I mentioned earlier, Windows falls back to NT AUTHORITY\SYSTEM when it doesn't have a user context yet.

    Hope this makes at least some sense :blobcatgoogly2:

    infosec.exchange/@kallisti/116

    #LegacyHive #NightmareEclipse

  3. New blog post!

    The title should be self-explanatory, it's an appreciation post for Nightmare Eclipse.

    You might notice that the tone is a bit more emotional/angry than my usual style of writing.
    This one's personal.

    ti-kallisti.com/infosec/ms/nig

    #NightmareEclipse #Microsoft #Hackers #InfoSec #SecurityResearch #ChainsawMan #Reze

  4. Der Security Forscher, der unter dem Namen Nightmare Eclipse oder Chaotic Eclipse bekannt ist, ist auf Grund von Zensur durch Google von Blogger zu Projectnightcrawler gewechselt.
    Sein neuster Blogpost findet sich hier:
    blog.projectnightcrawler.dev/p

    #nightmareeclipse #chaoticeclipse #microsoft #microslop #security #zeroday

  5. Looks like Nightmare Eclipse is in his limit.

    If that's the case, thank you for your service, exposing how shitty MSRC is.

    And how broken responsible disclosure in general.

    I hope you get your justice, and we can improve as industry moving forward.

    #cybersecurity #infosec #nightmareEclipse #windows #msrc

  6. If you're curious about what happened to #NightmareEclipse, they have moved to their own privately hosted Git server since both Github and Gitlab booted them. You can check their repos out at:

    git.projectnightcrawler.dev/

    Just be aware that download protections in your browser may block some of the downloads, so you may have to disable that temporarily.

    #Security #CyberSecurity

  7. Another bitlocker vuln from yours truly, now called GreatXML.

    Details below are copy pasted from NightmareEclipse readme:

    Steps to reproduce:

    1. If defender offline scan was initiated in the victim machine at any point then there is no need to login, the machine is automatically vulnerable. You will have to copy "unattend.xml" and "Recovery" directory to the root of the recovery partition then reboot to WinRE using shift + click on restart button, if everything was done correctly, a shell with unrestricted access to the bitlocker volume will spawn.

    2 .If defender offline scan was never initiated then you have to either login and initiate it yourself or figure out a way to boot into WinRE in offline scan state (I believe it should be very possible to do so without logging in) and follow steps above.

    Source and repo list:

    deadeclipse666.blogspot.com/20
    github.com/MSNightmare/GreatXML

    git.projectnightcrawler.dev/Ni

    git.churchofmalware.org/Nightm

    #cybersecurity #infosec #nightmareEclipse #greatxml #windows #zeroday #vulnerability #msrc

  8. Locked in heated rivalry with researcher, #Microsoft fixes 0-day they disclosed

    Microsoft on Tuesday released fixes for two high-severity zero-days that were disclosed by a researcher who has been locked in a testy beef with the software giant.

    #NightmareEclipse , the #pseudonym the researcher goes by, released a handful of high-severity #vulnerabilities in recent months, making them zero-days that had the potential to be #exploited in the wild. The researcher has said the disclosures, which included proof-of-concept code, came after Microsoft reneged on an arrangement the two made regarding vulnerabilities they had discussed.
    #security #0day #zeroday

    arstechnica.com/security/2026/

  9. Hey Windows (ab)users! Microsoft patched around 200 vulnerabilities in Windows etc today, a record Patch Tuesday batch. All indications are they fixed two of the zero-days dropped last month by the researcher Nightmare Eclipse, including "Green Plasma" and the "YellowKey" exploit that allowed local access to data encrypted by BitLocker. In response to today's Patch Tuesday, Nightmare Eclipse dropped an exploit for what they claimed was a zero-day bug in Windows Defender.

    Nearly three dozen of the bugs patched this month earned Microsoft’s most dire “critical” rating, and exploit code for at least three of the weaknesses is now publicly available.

    krebsonsecurity.com/2026/06/a-

    #patchtuesday #windows #nightmareeclipse #greenplasma #yellowkey

  10. Microsoft's Bug Bounty Betrayal Puts Everyone in Danger

    In this video I discuss how Microsoft's refusal to pay out on bug bounties is dissolving trust between them and security researchers causing them to no longer take on bug bounties and in some cases just release public exploits for Microsoft's software.

    youtube.com/watch?v=fL9HzADcTsY

    #MS #MaliciousSoftware #exploits #NightmareEclipse

  11. We will come to a point where you will make more money exploiting an undisclosed CVE than trying to parley with Microsoft Security Response Center.

    youtube.com/watch?v=9kxx5xp5nTQ

    You can make their team moving by simply disclosing publicly.

    Or better, you don't use Microsoft products.

    #Technology #CyberSecurity #CVE #Programming #Coding #Code #Security #Microsoft #MSRC #GitHub #NightmareEclipse

  12. Nightmare-Eclipse's public github repos (2026-05-25) : Nightmare-Eclipse : Free Download, Borrow, and Streaming : Internet Archive

    archive.org/details/nightmare-

    > Microslop wanted these repos gone. You can't kill a hydra, Microslop.
    lic github repos that were published by Nightmare-Eclipse as of May 25th, 2026.

    The 7zip (.7z) file in repos.zip contains the following Nightmare-Eclipse repos:

    BlueHammer

    GreenPlasma

    MiniPlasma

    RedSun

    UnDefend

    YellowKey

    github.com/Nightmare-Eclipse

    gitlab.com/nightmare-eclipse

    cybernews.com/security/github-

    The password for the 7zip (.7z) file in repos.zip is the first word in this description box.

    No data within the repos were altered in any way.

    #nightmareeclipse #backup #repository #archiveorg

  13. #Microsoft is under fire for threatening #securityresearcher #NightmareEclipse with legal action and criminal investigation after they publicly disclosed unpatched #vulnerabilities in Microsoft products. Nightmare Eclipse claims they were mistreated by Microsoft and had no choice but to disclose the vulnerabilities publicly. techcrunch.com/2026/05/29/micr #tech #media #news

  14. Scheinbar die neue Microsoft-Zero-Day-Strategie 2026:
    1. Sicherheitslücken nicht oder unzureichend patchen ✅
    2. GitHub-Konto des Reporters löschen ✅
    3. Mit Strafverfolgung drohen ✅
    4. MSRC-Konto des Reporters sperren & Fragen ignorieren ✅
    Kein Patch, dafür ein Anwalt und beim MSRC, das mal einen guten Ruf hatte, spart man lieber am kompetenten Personal.
    #Microsoft #Security #ZeroDay #NightmareEclipse
    heise.de/news/Zu-viele-Zero-Da

  15. Da rappelt es: Das GitLab-Konto von #NightMareEclipse wurde auch gesperrt und #Microsoft schreibt, dass die "unkoordinierte" Offenlegung von Schwachstellen nicht toleriert werde. Öl ins Feuer gießen, wenn Deeskalation angesagt wäre?

    borncity.com/blog/2026/05/28/n

  16. annnnnd #NightmareEclipse's gitlab account was just banned. what was that? 2 days?

  17. #NightmareEclipse reagiert auf #Microsoft Vorwürfe, gegen verantwortliche Offenlegungsverfahren zu verstoßen. Hat etwas von Rezzo "Zerstörung der CDU" und am 14. Juli soll es den großen Knall geben ... zieht euch warm an.

    borncity.com/blog/2026/05/25/z

  18. NightmareEclipse: yes the one who dropped Microsoft zero days threatened to drop something on July 14th.

    I wait your keeping annihilation of Microsoft 0days sir.

    deadeclipse666.blogspot.com/20

    Their new repo bcz Github flagged/deleted it: gitlab.com/nightmare-eclipse

    #NightmareEclipse #microsoft #0day #cybersecurity #infosec