# FastUnlock: Windows Narrator Lock Screen Bypass Zero-Day (No CVE) Released by Chaotic Eclipse

> Researcher Chaotic Eclipse (aka Nightmare-Eclipse / MSNightmare / INFINITE NIGHTMARE) publicly released FastUnlock, an unpatched Windows 11 zero-day in how Narrator handles its UI in a locked-account context. From the Microsoft-account 'I forgot my PIN' recovery screen, a physically present attacker can reach Narrator settings via keyboard and execute a binary from a USB stick as WsiAccount; the researcher also claims a BitLocker bypass.

- **Published:** 2026-11-19T22:47:11Z
- **Last reviewed:** 2026-11-20T15:25:19.973Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6507
- **ID:** TL-2026-6507
- **Severity:** HIGH
- **Category:** ZERO_DAY
- **Status:** ACTIVE
- **Actor:** Chaotic Eclipse
- **Detections:** 9 (1 shown free below) · **IOCs:** 23 (3 shown free below)

## Description

FastUnlock was published on 2026-11-19 (Security Affairs coverage) with a GitHub README at MSNightmare/FastUnlock (MIT license, README.md and LICENSE only; no binaries or hashes are shipped). The researcher states the flaw exists 'in the way how narrator handles UI in a locked account context': Microsoft did not ensure that newer Narrator UI does not run when launched in the context of a lock-screen user. The README says the new UI still carries older code that prevents it from spawning as SYSTEM, so execution lands in the context of the WsiAccount user instead.

The reproduction steps documented by the researcher: (1) at the Microsoft account window's reset prompt ('I forgot my PIN' / password option), press Win+U and enable Narrator; (2) Narrator focuses a hidden Narrator-owned background window; (3) hold CAPS and use the arrow keys to reach the 'Next' button and then 'Math reading settings', and press CAPS+Enter to open the settings window; (4) navigate Bluetooth & Devices > AutoPlay > Removable Drive > 'Open folder to view files (File Explorer)'; (5) insert a USB stick, after which Narrator focuses Explorer and the binary on the stick is executed as WsiAccount. Several alternative paths to code execution exist according to the researcher. Per Security Affairs, the researcher did not demonstrate the final USB-execution step because he lacked a USB stick, so the complete code-execution chain is not independently shown.

Prerequisites: physical access and at least one local user account linked to an online (Microsoft) account. The researcher claims he breached a fully encrypted Windows 11 26H2 machine with the November 2026 update installed in about five minutes, i.e. a BitLocker bypass. Only Windows 11 26H2 (November patch) was tested; the researcher states he has not checked other versions (including Windows 10). The README compares it favorably to the earlier lock-screen bypass ZDI-21-1053 (CVE-2021-26431 per ZDI mapping) as more convenient. The README advises users to 'hold tight any windows machines until Microsoft patches this', implying it was unpatched at release.

As of the sources reviewed, no CVE, CVSS score, Microsoft statement, patch, or in-the-wild exploitation has been reported, and no network IOCs or file hashes exist. Severity (HIGH) is an analyst estimate reflecting the physical-access requirement against full-disk-encrypted endpoints (e.g., lost or stolen laptops). The release continues a pattern of public zero-day drops by this researcher (Abdelhamid Naceri, a former Microsoft employee per SecurityWeek/Security Affairs): UnDefend and RedSun (Defender), BigDiskBuster (Defender update DoS, September 2026; Microsoft says Defender detects and prevents observed activity), GreenSection (Nvidia memory corruption), ShieldCrash (Defender), HardBreacher (Kaspersky Endpoint Security LPE), PrettyPrague (GenDigital/Avast LPE) and FalconFlank (CrowdStrike Falcon LPE). Earlier 2026 releases YellowKey and GreatXML were also reported as BitLocker bypasses (secondary search coverage only).

Defender guidance: treat as unpatched; enforce BitLocker with pre-boot authentication (TPM+PIN), restrict physical access, disable USB/AutoPlay on lock screen where feasible, and monitor for Narrator launching on the sign-in/lock screen followed by unexpected processes under the WsiAccount context. Note the researcher previously rejected BitLocker PIN as a sufficient mitigation for YellowKey; efficacy against FastUnlock is unverified.

## MITRE ATT&CK

- T1546.008 Event Triggered Execution: Accessibility Features
- T1005 Data from Local System
- T1200 Hardware Additions
- T1211 Exploitation for Defense Evasion

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**FastUnlock Post-Exploitation — Shell, Account and Persistence Tooling as WsiAccount** (`TL-2026-6507-SPL-002`)

Detects follow-on activity after FastUnlock code execution (TL-2026-6507): shells, script hosts, net/sc/schtasks/reg utilities and BitLocker-state queries running as WsiAccount, categorised into account manipulation (T1136.001), scheduled task or service persistence (T1053.005), accessibility-feature persistence (T1546.008) and discovery. Command execution under a lock-screen identity should not occur in normal operations.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1059, T1136.001, T1053.005, T1546.008
- **Data sources:** sysmon
- **Severity:** high
- **Confidence:** medium

### Splunk SPL

```spl
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 earliest=-24h User="*WsiAccount"
| where match(Image,"(?i).(cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|reg|schtasks|sc|net|net1|whoami|wmic|certutil|bitsadmin|vssadmin|manage-bde|icacls|takeown)[.]exe$")
| eval activity=case(match(CommandLine,"(?i)net1?[ ]+(user|localgroup)"),"account_manipulation_T1136.001", match(CommandLine,"(?i)(schtasks|sc)([.]exe)?[ ]+(/create|create|config)"),"scheduled_task_or_service_T1053.005", match(CommandLine,"(?i)Image File Execution Options|Accessibility.ATs"),"accessibility_persistence_T1546.008", match(CommandLine,"(?i)whoami|systeminfo|manage-bde|vssadmin"),"discovery_or_encryption_state", true(),"other_shell_activity")
| stats count min(_time) as first_seen max(_time) as last_seen values(Image) as images values(CommandLine) as command_lines values(ParentImage) as parents by host User activity
| convert ctime(first_seen) ctime(last_seen)
| sort - count
```

### Microsoft KQL

```kql
// FastUnlock (TL-2026-6507): post-exploitation shell, account, persistence and discovery activity as WsiAccount
DeviceProcessEvents
| where Timestamp > ago(24h)
| where AccountName =~ "wsiaccount"
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "reg.exe", "schtasks.exe", "sc.exe", "net.exe", "net1.exe", "whoami.exe", "wmic.exe", "certutil.exe", "bitsadmin.exe", "vssadmin.exe", "manage-bde.exe", "icacls.exe", "takeown.exe")
| extend Activity = case(
    ProcessCommandLine matches regex "(?i)net1?[ ]+(user|localgroup)", "account_manipulation_T1136.001",
    ProcessCommandLine matches regex "(?i)(schtasks|sc)([.]exe)?[ ]+(/create|create|config)", "scheduled_task_or_service_T1053.005",
    ProcessCommandLine has_any ("Image File Execution Options", "ATs"), "accessibility_persistence_T1546.008",
    ProcessCommandLine has_any ("whoami", "systeminfo", "manage-bde", "vssadmin"), "discovery_or_encryption_state",
    "other_shell_activity")
| project Timestamp, DeviceName, AccountDomain, AccountName, Activity, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA256
| order by Timestamp desc
```

### Sigma

```yaml
title: FastUnlock Shell and Persistence Tooling Run as WsiAccount
id: 91c8e2b4-5d7a-4b36-a1f9-3e60d2c8b7a4
status: experimental
description: Detects shells, script hosts, account, service and scheduled-task utilities and encryption-state queries executed as the WsiAccount identity. After FastUnlock lands execution at the lock screen an attacker typically uses these to create accounts, persist and inspect BitLocker state.
references:
    - https://github.com/MSNightmare/FastUnlock
    - https://securityaffairs.com/203537/hacking/chaotic-eclipse-releases-fastunlock-a-new-windows-zero-day-vulnerability.html
author: Threadlinqs Team
date: 2026-11-19
tags:
    - attack.execution
    - attack.t1059
    - attack.persistence
    - attack.t1136.001
    - attack.t1053.005
    - attack.t1546.008
logsource:
    category: process_creation
    product: windows
detection:
    selection_user:
        User|endswith: '\WsiAccount'
    selection_img:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
            - '\pwsh.exe'
            - '\wscript.exe'
            - '\cscript.exe'
            - '\mshta.exe'
            - '\rundll32.exe'
            - '\regsvr32.exe'
            - '\reg.exe'
            - '\schtasks.exe'
            - '\sc.exe'
            - '\net.exe'
            - '\net1.exe'
            - '\whoami.exe'
            - '\wmic.exe'
            - '\certutil.exe'
            - '\bitsadmin.exe'
            - '\vssadmin.exe'
            - '\manage-bde.exe'
    condition: selection_user and selection_img
falsepositives:
    - IT recovery tooling or remote-support agents run at the lock screen on managed devices
level: high

```

**Known false positives:**

- IT recovery tooling or remote-support agents that run commands at the lock screen
- Provisioning scripts that execute during OOBE under a transient local account

**Tuning notes:** Tune the allowed Image list per fleet. Add exclusions for known provisioning or management agents by ParentImage. Keep the activity=case() ordering so account and persistence commands are reported ahead of generic shell use. Consider pairing with Windows Security 4720/4732 (local account created / added to group) for corroboration.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- FastUnlock Narrator Chain — Narrator/Settings Spawning Explorer, Shell or Removable Binary (locked: unlock with TL Creds)
- FastUnlock Data Staging — WsiAccount File Activity on Removable Media or User Profiles (locked: unlock with TL Creds)
- FastUnlock Researcher Infrastructure — MSNightmare Repository/Video Access and WsiAccount Egress (locked: unlock with TL Creds)
- FastUnlock USB Payload — Removable-Drive Binary Executed as WsiAccount/SYSTEM (locked: unlock with TL Creds)
- Accessibility Feature Persistence — IFEO Debugger / ATs StartExe on Ease-of-Access Binaries (locked: unlock with TL Creds)
- Chaotic Eclipse Toolset and Defender Tampering — FastUnlock Follow-On (locked: unlock with TL Creds)
- FastUnlock Narrator Lock-Screen Bypass — Process Execution as WsiAccount (locked: unlock with TL Creds)
- FastUnlock Command-and-Control — Outbound Connections from WsiAccount or Removable-Drive Binaries (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (3 of 23)

Defanged, TLP:CLEAR.

- URL: `hxxps://www[.]youtube[.]com/watch?v=6BKsdUtc6bg`
- URL: `hxxps://cybersecuritynews[.]com/windows-11-narrator-lock-screen-0-day/`
- URL: `hxxps://secret[.]club/2021/01/29/touch-lockscreen-bypass.html`

Full set of 23 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Chaotic Eclipse Releases FastUnlock, a New Windows Zero-Day Vulnerability](https://securityaffairs.com/203537/hacking/chaotic-eclipse-releases-fastunlock-a-new-windows-zero-day-vulnerability.html)
- [FastUnlock: Windows Narrator LockScreen Bypass 0day Vulnerability (researcher GitHub)](https://github.com/MSNightmare/FastUnlock)
- [SecurityWeek: Nightmare Eclipse drops new Microsoft Defender exploit after revealing identity](https://www.securityweek.com/nightmare-eclipse-drops-new-microsoft-defender-exploit-after-revealing-identity/)
- [BigDiskBuster (researcher GitHub, prior release)](https://github.com/MSNightmare/BigDiskBuster)
- [ZDI-21-1053: Windows lock screen authentication bypass (earlier lock-screen bypass cited in README)](https://www.zerodayinitiative.com/advisories/ZDI-21-1053)
- [BitLocker Lockscreen bypass (secret.club, historical Narrator lock-screen research)](https://secret.club/2021/01/15/bitlocker-bypass.html)
- [Windows Zero-Days Expose BitLocker Bypasses (YellowKey/GreenPlasma, related researcher releases)](https://thehackernews.com/2026/05/windows-zero-days-expose-bitlocker.html)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple and Gold in full, 2 calls a day on a free account): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6507
