LegacyHive is a proof-of-concept elevation-of-privilege primitive targeting the Windows User Profile Service (ProfSvc), the component responsible for loading and unloading a signed-in user's registry hives (NTUSER.DAT and UsrClass.dat) at logon/logoff. The published technique allows a low-privileged, standard (non-administrator) local user to cause a hive belonging to a different local user account to be mounted underneath the attacker's own HKEY_CURRENT_USER\Software\Classes root, i.e., their per-user 'classes root'. Once mounted there, the victim's hive data — including UsrClass.dat contents such as COM/shell-extension registrations, file-association state, and other shell configuration — becomes readable/writable in a context the attacker fully controls, without the attacker ever needing SYSTEM or Administrator privileges to trigger the load.

The vulnerability class is not novel in kind: Microsoft has previously shipped at least three related fixes for User Profile Service / registry-hive-loading elevation-of-privilege bugs — MS15-003 (ProfSvc could be tricked, via a Shell Folders registry key change plus an NTFS junction, into opening an arbitrary UsrClass.dat belonging to another user), MS16-111 (RegLoadAppKey / NtLoadKeyEx hive-attachment-point abuse), and MS16-124 (NtLoadKeyEx read-only-hive-to-write-mode fallback with process impersonation leading to EoP). LegacyHive appears to be a modern recurrence of the same underlying pattern in current, fully-patched Windows builds, indicating the User Profile Service's hive-load path has not been durably hardened against this class of abuse.

The researcher, operating under the handles Nightmare-Eclipse, 'Chaotic Eclipse', and 'Dead Eclipse' (blog: deadeclipse666.blogspot.com), announced ahead of time that a 'major exploit targeting Microsoft products' would land on 2026-07-14, having previously claimed unspecified 'chains' were preventing an earlier release. On that date the LegacyHive GitHub repository (github.com/MSNightmare/LegacyHive, mirrored at git.projectnightcrawler.dev/NightmareEclipse/LegacyHive, MIT-licensed, C++) appeared, initially as a placeholder ('N/A' README, license file only, 2 commits), with full source (LegacyHive.cpp) and documentation following roughly 11 hours later (4 commits total). The researcher deliberately stripped the released PoC down from its original, more dangerous form: the internal/original version could reportedly load an arbitrary registry hive with no extra credentials, while the public build is artificially restricted to the UsrClass.dat hive only and requires the operator to already possess a second standard user's password plus the username of a third account (which can be an administrator account) before the primitive will fire. This restriction is a self-imposed abuse-reduction measure by the discloser, not a mitigation implemented by Microsoft.

LegacyHive is the latest in a six-exploit campaign by the same actor since April 2026, all targeting Microsoft Windows: BlueHammer (CVE-2026-33825, a TOCTOU race in Windows Defender's file-remediation engine using an NTFS junction to redirect a Defender write to C:\Windows\System32 for SYSTEM code execution — patched 2026-04-14, added to CISA KEV 2026-04-22/23, and confirmed by CISA on 2026-06-30 to be under active exploitation by ransomware gangs), RedSun (an alternate Defender privilege-escalation path to SYSTEM, silently patched, no CVE assigned), UnDefend (a Defender-disruption tool that weakens detection while masking reported system health), YellowKey (a BitLocker bypass affecting TPM-only configurations, exploitable with physical device access), GreenPlasma (a partial Windows LPE PoC released as a building block rather than a complete exploit), and MiniPlasma (an LPE tied to a supposedly-already-fixed 2020-era vulnerability, confirmed by researchers to still work on fully patched Windows 11 as of May 2026). The actor has publicly stated a grievance-driven motive ('someone violated our agreement and left me homeless with nothing'), alleged direct threats from MSRC personnel, and has promised further RCE disclosures plus a 'dead man's switch' for automatic exploit release; Huntress Labs linked April 2026 exploitation activity to Russian-geolocated infrastructure, and some evidence (demonstrated insider-level Windows codebase knowledge) has fueled speculation of a former Microsoft employee or contractor, though attribution remains unconfirmed.

As of disclosure (2026-07-15), Microsoft has not assigned a CVE ID, published a security advisory, or shipped a patch for LegacyHive specifically. The PoC was independently verified by the discloser to function against 'all currently supported desktop and server' Windows builds with the July 2026 Patch Tuesday security updates applied (that cycle addressed roughly 570 vulnerabilities including 3 separate zero-days), meaning the flaw survived Microsoft's most recent monthly patch cycle. No in-the-wild exploitation, malware integration, or threat-actor weaponization of LegacyHive itself has been reported; unlike BlueHammer, this is presently a disclosed research primitive rather than an observed ransomware-enabling campaign. Given the same actor's track record (BlueHammer went from PoC to CISA-KEV-listed ransomware tooling within under three months), defenders should treat LegacyHive as a credible, unpatched local elevation/lateral-disclosure vector on multi-user Windows hosts (terminal servers, shared workstations, RDS/VDI) pending an official Microsoft fix, and should assume the actor may escalate, weaponize, or chain it with future disclosures.