Back to Technology
Microsoft's Defender Fix Backfires: New Patch May Let Hackers Brick Your Storage
Technology

Microsoft's Defender Fix Backfires: New Patch May Let Hackers Brick Your Storage

Jul 100 views

Key takeaways

  • Microsoft's Wednesday patch for the RoguePlanet (CVE-2026-50656) zero-day may itself introduce a disk-exhaustion attack vector via SpyNet and mpengine.dll behavior.
  • Researcher NightmareEclipse found that Defender's new code bypasses normal file-size limits when caching Zone.Identifier metadata streams, exploitable via a rogue SMB server.
  • The disclosure deepens an ongoing public feud between NightmareEclipse and Microsoft stemming from a silent patch dispute that began in May.

What was supposed to be a security win for Microsoft has turned into another headache. A patch released Wednesday to address a serious zero-day vulnerability in the Windows Defender security engine appears to have introduced its own potentially dangerous behavior — one that could allow attackers to completely exhaust available disk space on a targeted Windows machine. The researcher who originally uncovered the flaw, operating under the pseudonym NightmareEclipse, was quick to flag the newly introduced problem just a day after the fix went live.

The original vulnerability, tracked as CVE-2026-50656 and dubbed RoguePlanet, first came to public attention in June when NightmareEclipse disclosed both details of the flaw and working exploit code. The vulnerability is serious: it allows remote attackers to gain administrative control over Windows 10 and Windows 11 systems, even when real-time protection is turned off. Microsoft patched it through an update to the Microsoft Malware Protection Engine — the core component underpinning Windows Defender — which automatically downloads and installs without requiring user action.

The trouble lies in the so-called 'defense-in-depth' additions bundled alongside the fix. According to NightmareEclipse, new code within mpengine.dll — the driver tied to Microsoft's Malware Protection Engine — can in certain circumstances cause an 8-byte data leak each time it attempts to open a file. Compounding matters, updated functionality within SpyNet, Microsoft's cloud reporting service for suspicious software activity, interacts with this behavior in a way that could trigger massive, uncapped file writes to local storage.

Normally, Windows Defender enforces strict size limits on files written during scanning and quarantine processes to prevent precisely this kind of storage exhaustion. However, NightmareEclipse identified an exception: the SpyNet-related functions inside mpengine.dll will cache a local copy of a Zone.Identifier alternative data stream regardless of the file's size. A Zone.Identifier is a hidden metadata file Windows automatically attaches to files downloaded from the internet or external sources. An attacker could exploit this using a specially crafted SMB server — a standard Windows file-sharing protocol — by serving a malicious file alongside an enormous associated Zone.Identifier stream, then stalling the connection to keep Defender locked and the disk perpetually occupied.

Microsoft did not immediately respond to requests for comment confirming whether this behavior exists in the patched build. The episode is just the latest chapter in a prolonged and increasingly hostile dispute between the company and NightmareEclipse, which began in May after the researcher alleged Microsoft had silently patched a vulnerability they had privately reported without proper credit. That grievance triggered a wave of public zero-day disclosures before patches were ready, prompting Microsoft to publicly criticize NightmareEclipse for irresponsible disclosure and hint at possible legal action — a threat it later walked back following significant public backlash.

The bigger picture

The situation Microsoft now finds itself in is an almost textbook example of how poorly managed vulnerability relationships can spiral into compounding security risks. When a company silently incorporates a researcher's work without acknowledgment, it signals to the broader security community that private, cooperative disclosure carries little upside. NightmareEclipse's decision to go public with subsequent findings before patches were ready was undoubtedly disruptive, but the chain of events that led there is worth examining. Microsoft's initial behavior set a precedent that eroded the trust underpinning coordinated disclosure.

What makes this latest development particularly damaging for Microsoft is the optics. Security patches are expected to close doors, not open new ones. The fact that a defense-in-depth addition — code explicitly designed to add layers of protection — is the source of a potential disk-filling vector will raise serious questions about the rigor of Microsoft's internal patch review processes. Enterprises running Windows Defender at scale have little tolerance for updates that could destabilize systems, and this incident may accelerate conversations about supplementary endpoint security tools from third-party vendors.

Readers should watch for two things in the coming weeks. First, whether Microsoft issues a follow-up fix or public statement acknowledging the behavior NightmareEclipse described — silence will only deepen skepticism. Second, whether this ongoing feud produces more pre-patch disclosures. NightmareEclipse has already demonstrated a pattern of rapid, retaliatory publication. If the relationship between the researcher and Microsoft does not stabilize through some form of structured engagement — perhaps through a proper bug bounty arrangement or neutral third-party mediation — the security community should expect more turbulence ahead.

LagPing's take

We decided to cover this story because it sits at the intersection of two issues we think matter deeply to our readers: the technical realities of software security and the very human drama of how companies treat the researchers who help keep their products safe. Microsoft is one of the most consequential software companies on the planet, and Windows Defender sits on hundreds of millions of machines — so when a patch for that system potentially introduces new attack surface, that is not an abstract concern. It affects everyday users, IT administrators, and enterprise environments alike. We also think the NightmareEclipse dispute deserves more nuanced coverage than it typically gets. The binary framing of 'responsible versus irresponsible disclosure' often obscures the very real power imbalance between independent researchers and major corporations. This story is a reminder that vulnerability research is not just a technical discipline — it is a relationship, and when that relationship breaks down, everyone pays a price. We'll be following this closely.

Find "Hard Drive" on Amazon

As an Amazon Associate, LagPing earns from qualifying purchases. Product links are affiliate links.

You might also like