<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/microsoft/</link><description>Recent content in Microsoft on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 13:29:52 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/microsoft/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Signed 11 Files That Bypass Secure Boot</title><link>https://hackingpassion.com/secure-boot-shim-bypass/</link><pubDate>Wed, 15 Jul 2026 13:29:52 +0200</pubDate><guid>https://hackingpassion.com/secure-boot-shim-bypass/</guid><description>&lt;p>&lt;strong>Some malware loads before Windows even starts, before your antivirus exists.&lt;/strong> It survives a full reinstall, and 11 files signed by Microsoft are all it takes.&lt;/p>
&lt;p>One check is supposed to make that impossible. These 11 get past it, on almost any PC.&lt;/p>
&lt;p>ESET&amp;rsquo;s Martin Smolár published this on July 14. The files are old, some more than ten years old, and each one carries a valid Microsoft signature.&lt;/p>
&lt;p>When you turn on your computer, something runs before Windows does. It is the firmware, the low-level code built into the machine, and its job is to load the thing that loads Windows. Secure Boot is the check that runs at that moment. It looks at each piece of startup code and asks one question: is this signed by someone I trust? If the answer is yes, it runs. If no, it stops.&lt;/p></description></item><item><title>Windows Hands Your Name to the Police Through One Hidden Number</title><link>https://hackingpassion.com/windows-gdid-tracking/</link><pubDate>Wed, 08 Jul 2026 11:29:27 +0200</pubDate><guid>https://hackingpassion.com/windows-gdid-tracking/</guid><description>&lt;p>You are &lt;strong>completely anonymous&lt;/strong> and think no one can trace you. But Windows put a &lt;strong>permanent number on your machine&lt;/strong>, it never turns off, and that number is where the police start when they want your name. That is exactly &lt;strong>how the FBI&lt;/strong> just caught a 19-year-old hacker who thought he had &lt;strong>covered every track&lt;/strong>.&lt;/p>
&lt;p>On July 1, US prosecutors in Chicago made their case public against a 19-year-old named &lt;strong>Peter Stokes&lt;/strong>, who holds both a US and an Estonian passport. They say he runs with &lt;strong>Scattered Spider&lt;/strong>, one of the biggest crews in cybercrime, the kind that breaks into companies and then demands money to leave them alone. He has not been found guilty of anything, and under the law he stays &lt;strong>innocent until a court says otherwise&lt;/strong>.&lt;/p></description></item><item><title>The Miasma Worm Hid in Microsoft's Code and Ran the Moment You Opened It</title><link>https://hackingpassion.com/miasma-worm-ai-coding-agents/</link><pubDate>Thu, 11 Jun 2026 12:08:30 +0200</pubDate><guid>https://hackingpassion.com/miasma-worm-ai-coding-agents/</guid><description>&lt;p>GitHub disabled &lt;strong>73 of Microsoft&amp;rsquo;s own repositories in 105 seconds&lt;/strong>, after a worm called &lt;strong>Miasma&lt;/strong> planted a credential stealer inside Microsoft&amp;rsquo;s Azure code on GitHub.&lt;/p>
&lt;p>The part that makes this different is how it ran. A developer did not need to build the project or install a package. &lt;strong>Opening one of those repositories in an AI editor, VS Code, Claude Code, Cursor, or Gemini, was enough to set it off.&lt;/strong> 😱&lt;/p></description></item><item><title>RedSun and UnDefend: Two Unpatched Windows Defender Zero-Days</title><link>https://hackingpassion.com/redsun-undefend-defender-zero-days/</link><pubDate>Sun, 19 Apr 2026 10:57:14 +0200</pubDate><guid>https://hackingpassion.com/redsun-undefend-defender-zero-days/</guid><description>&lt;p>Two unpatched Windows Defender zero-days have been actively exploited since &lt;strong>April 16th&lt;/strong>, and both of them work on fully patched &lt;strong>Windows 10&lt;/strong>, &lt;strong>Windows 11&lt;/strong>, and &lt;strong>Server 2019&lt;/strong> and later, including machines that installed this month&amp;rsquo;s Patch Tuesday updates. One of them makes Defender write the attacker&amp;rsquo;s payload into &lt;strong>System32&lt;/strong> by itself, then stands back and lets Windows run it as &lt;strong>SYSTEM&lt;/strong>. The other blocks Defender from receiving any new virus definitions and lies to the EDR management console about it, showing green checkmarks on machines that are already fully compromised. 😏&lt;/p></description></item><item><title>Why It Took Microsoft 32 Years to Disable NTLM</title><link>https://hackingpassion.com/ntlm-finally-disabled/</link><pubDate>Wed, 04 Feb 2026 11:31:37 +0100</pubDate><guid>https://hackingpassion.com/ntlm-finally-disabled/</guid><description>&lt;p>32 years. That is how long it took Microsoft to disable NTLM, the protocol that handles Windows login authentication. A broken system linked to $10 billion in damages and some of the worst cyberattacks ever recorded. Hackers have been exploiting it since 2001. Here is the story of why it took this long.&lt;/p>
&lt;p>On January 30, 2026, Microsoft announced they will finally disable NTLM by default in future Windows releases.&lt;/p></description></item><item><title>One Windows Update, Ten Problems, Two Emergency Patches</title><link>https://hackingpassion.com/windows-one-update-ten-problems/</link><pubDate>Wed, 28 Jan 2026 14:10:10 +0100</pubDate><guid>https://hackingpassion.com/windows-one-update-ten-problems/</guid><description>&lt;p>Microsoft pushed one security update. It broke at least 10 different things. 114 security fixes. Two emergency patches. PCs that won&amp;rsquo;t boot. Outlook that crashes. Remote Desktop that fails. Shutdown buttons that do nothing. And Microsoft is still investigating why some systems show a black screen and never start again. 🧐&lt;/p>
&lt;p>&lt;strong>A Windows and Microsoft story that keeps getting worse.&lt;/strong>&lt;/p>
&lt;p>This was one of the largest Patch Tuesday releases in history. 114 vulnerabilities fixed, 8 rated Critical, 106 Important. The breakdown: 57 privilege escalation flaws, 22 remote code execution bugs, and 22 information disclosure vulnerabilities. Three zero-days in total, one actively exploited in the wild and two publicly known before Microsoft could patch them. In 2025 alone, Microsoft patched 1,130 CVEs across the year, 12% more than 2024.&lt;/p></description></item></channel></rss>