
Another Scattered Spider bust – Bling-swinging suspect extradited to US
Where did you take yourself on vacation at 17? How about Paris, Italy, Spain, Germany, New York, Florida, New Mexico, Thailand, and Dubai?


We’ve written about Nightmare Eclipse (NE) several times before, not least because of the way their exploits work, and the way their releases are timed.
Many of NE’s attacks are notable because:
Well, NE’s latest writeup is entitled FastUnlock, and it’s subtitled Windows Narrator LockScreen Bypass 0day Vulnerability.
It’s not their only zero-day this month – the first was an exploit from just over a week ago dubbed SignDrop, which did come out on Exploit Wedneday, and did claim to exploit Defender.
I tried pretty hard to get the SignDrop exploit to work in a realistic test environment, but failed. However, I didn’t go as far as satisfying myself that it couldn’t be made to work, or that I had magically happened upon system settings that would reliably prevent it.
The FastUnlock reveal apparently wasn’t timed for maximum effect, because Patch Tuesday was more than a week ago, and wasn’t aimed at embarrassing Microsoft by specifically targeting Windows Defender.
But NE does stress the point – perhaps inserted as a bit of an afterthought in an update to the original exploit that added the words “an issue caused by total negligence from Microsoft’s side” to the writeup – that it could represent a practical bypass of BitLocker.
That’s because, on many laptops, a BitLocker-encrypted hard disk will automatically be unlocked by the time the lock screen bypass happens. (There are various unstated assumptions in that claim, which we’ll cover in “What to do?” at the end.)
The fascinating thing about this exploit is that it doesn’t need any coding, scripting, or other skills traditionally seen as necessities for hacking, reversing, finding, and fine-tuning attacks.
Simply put, it relies on you having your Windows logon tied to an online account – something that you’re forced to do in a routine install of Windows these days unless you make a special effort to avoid it – and on the way the Windows Narrator feature works.
(NE notes that the attack worked on Windows 11 26H2, the very latest release, with the November 2026 security patches installed, but only speculates that it might work under earlier Windows releases.)
Narrator is a Windows accessibility feature that acts as a screen reader, so that your computer will speak aloud the content of popups, dialogs and so on in case you can’t read them, and will tell you which clickable buttons or links you’ve landed on to help you choose the right one.
}
The problem here, says NE, is that if your Windows account isn’t local, you get a helpful “I forgot my PIN” or “I forgot my password” link on the lock screen, and if you activate Narrator after clicking on that special link, the Narrator process runs as a special user called WsiAccount, where the letters Wsi are short for Web sign-in.
Apparently, the Narrator subsystem ensures that it’s not running under the special account SYSTEM before activating, a useful precaution to prevent it being abused to hack into software such as privileged Windows services that rely on this all-powerful level of local access.
But it doesn’t check for WsiAccount, and in NE’s exploit, activating Narrator and then opening up its Accessibility page in the Windows Settings utility leads to an invisible window that can be abused to run programs of your choice under the WsiAccount identity.
That gives you a pathway to access the computer, even though you haven’t yet logged on yourself, and couldn’t do so anyway because you don’t know the legitimate laptop user’s password.
And if BitLocker was set up in its default mode, where the decryption key is supplied automatically but securely at startup by the special security chip known as a Trusted Platform Module (TPM) that Windows 11 insists you have․․․
․․․then by the time the lock screen or logon screen appears, the hard disk has already been quietly unlocked by Windows in the background.
This means the security against laptop thieves breaking out of the logon process and accessing the C:\ drive is entirely down to the correctness and resilience of the Windows authentication process.
As NE points out, if you can get into the Settings > Accessibility menu, albeit without being able to see what you’re doing, you can navigate through its menu options and clickable links via special keypresses, so you don’t need to guess where the mouse cursor is pointing.
For example, you can go across, up and down again in the Settings menu hierarchy, get into the Bluetooth & devices > AutoPlay screen, and enable the automatic launch of File Explorer when you plug in a USB drive.
Then, you can plug in a USB drive with utilities and hacking tools of your choice, and launch those programs as WsiAccount, with the files on C:\ already unlocked by BitLocker and mounted for use by the operating system.
The current much-trumpeted spate of AI-inspired vulnerabilty disclosures has focused a spotlight on the once-a-month patching processes that many vendors have deliberately injected into our system administration lifestyles over more than two decades.
So, the upside of what some observers have been hyping up as a vulnocalypse, as though we are all doomed and might as well submit to our new robot overlords right now, is that the world is starting to accept that the concept of security-by-regular-but-infrequent-calendar-appointments has never been the right way to look at cybersecurity, and that we should move away from it wholeheartedly.
Also, and perhaps ironically given that NE’s full-disclosure bug reports so far seem to stem from a long-running personal beef with Microsoft, those very disclosures have focused a spotlight on Microsoft’s patching and vulnerability reporting processes.
Indeed, Microsoft implicitly threatened security researchers with legal trouble earlier this year:
Uncoordinated disclosures that put proof-of-concept code for unpatched vulnerabilities into the hands of bad actors are never justifiable and have real-world consequences. Our security teams across the company work tirelessly tracking threat actors who look for weaknesses just like these to attack Microsoft and our customers. Our Digital Crimes Unit will continue bringing cases against these actors and those that enable their criminal activity – coordinating as needed with law enforcement around the world.
However, the online response to this bold statement did not produce the public support that Microsoft seems to have expected.
The company’s insistence that it should always have the final say about how bugs in its products were reported was vocally criticised.
As David Emerson, SolCyber CTO and my co-host on the monthly SolCyber podcast TALES FROM THE SOC, explained:
I think that there are many, many ways to behave, and many ways to disclose a bug. And I don’t think Microsoft is in control of either of those things. I don’t think anyone is obligated to tell Microsoft about things that they have found. I don’t think anyone’s obligated to alert Microsoft before publishing a bug in its software, and I don’t think anyone’s obligated to ensure that their exploits work 100%.
And Microft is going to have to navigate that freedom, because that freedom could potentially open up a lot of free labor on the part of the community to help Microsoft’s products get better.
NE, who had summarily been kicked off Microsoft’s GitHub platform earlier in the year, and who was clearly one of “these actors” against whom Microsoft would “continue bringing cases,” was ultimately allowed back, and Microsoft publicly climbed down from its high horse.

TPMandPIN mode with Bitlocker. This means that you always need to enter an BitLocker unlock code at startup, so a laptop thief can’t get directly to your Windows logon screen just by turning on your computer. You can even go for a “PIN” with both letters and numbers (in reality, a proper passphrase) if your sysadmin will let you. It’s a tiny bit of inconvenience for a lot more safety and security.
Why not ask how SolCyber can help you do cybersecurity in the most human-friendly way? Don’t get stuck behind an ever-expanding convoy of security tools that leave you at the whim of policies and procedures that are dictated by the tools, even though they don’t suit your IT team, your colleagues, or your customers!
Paul Ducklin is a respected expert with more than 30 years of experience as a programmer, reverser, researcher and educator in the cybersecurity industry. Duck, as he is known, is also a globally respected writer, presenter and podcaster with an unmatched knack for explaining even the most complex technical issues in plain English. Read, learn, enjoy!

Where did you take yourself on vacation at 17? How about Paris, Italy, Spain, Germany, New York, Florida, New Mexico, Thailand, and Dubai?

Can’t process or ship orders, can’t say how long it will take to fix.

Here are five solid reasons why now is the right time to look into cyber insurance.

By subscribing you agree to our Privacy Policy and provide consent to receive updates from our company.






