RC RANDOM CHAOS

Windows Narrator launches programs on a locked machine

FastUnlock, an unpatched Windows technique, uses Narrator to run programs from the lock screen in a limited account, with no fix yet. What it needs and how to limit exposure.

· 3 min read
Windows Narrator launches programs on a locked machine

A researcher going by MSNightmare, also Nightmare Eclipse, posted a technique yesterday that uses Narrator, the Windows screen reader built into the lock screen, to launch programs on a locked machine without anyone signing in. ThreatLocker tested it the same day and confirmed it works. Microsoft has no fix out.

The payoff is limited. In ThreatLocker’s test the technique landed in an account the firm identified as WSIAccount, which it said is “not an administrator account.” So this is program execution from the lock screen under a restricted identity, not a route to administrator control. That is useful to someone holding your laptop, and less sweeping than a lock-screen bypass sounds at first.

It does not work on every machine. Two conditions have to hold: physical access to the computer, and a Microsoft account reachable through the lock screen’s recovery options. The researcher’s own disclosure on GitHub is thin, a video and a few words, so the clearest description of the behaviour is ThreatLocker’s independent test rather than the original post.

The BitLocker question is worth being precise about, because a lot of people assume full-disk encryption covers this. In the common setup, it does not. When BitLocker is backed by a TPM with no startup PIN, the TPM unlocks the drive automatically at boot. By the time the lock screen is drawn, the drive is already decrypted and the files are readable. FastUnlock runs at exactly that point. It does not break that encryption or recover the key. Microsoft’s own TPM documentation describes this mode, where the drive unlocks “without having to enter a PIN.”

That makes this a smaller problem than cracking an encrypted disk, and a real one anyway for a machine sitting in someone else’s hands.

No official list of affected Windows versions exists yet, and nothing suggests the technique has been used in a real attack. Treat any machine that meets the two conditions as possibly affected until Microsoft says otherwise.

What to do now

With no patch, the useful steps are about physical control and what the machine does at startup.

Add a startup PIN to BitLocker on sensitive machines. That forces a secret before the TPM releases the key, closing the window FastUnlock runs in. It only helps on a machine that has not yet booted to the lock screen.

Shut down or hibernate devices when they leave someone’s control. A startup PIN protects a powered-off machine, not one already sitting at the lock screen with its drive decrypted.

Keep machines that can wander out of reach: laptops, shared desks, front-counter terminals that a stranger could walk up to.

Microsoft’s countermeasures guidance already points the same way for determined, hands-on attackers: a startup PIN plus shutting down or hibernating when the machine is out of your control. That guidance predates this technique and happens to cover it. Watch for an advisory and apply it when it lands.

Share

Keep Reading

Latest on the Wire

Full wire →

New signal daily · RSS

Stay in the loop

New writing delivered when it's ready. No schedule, no spam.