LoFP LoFP / legitimate device registrations may coincidentally use the `10.0.19041.928` build (windows 10 20h1) with a default `desktop-` hostname, particularly on imaged or unmanaged windows hosts that have not been updated. validate against your device inventory, expected provisioning workflows, and the registering user before escalating.

Sample rules

Entra ID Device Registration with ROADtools Default OS Build

Description

Identifies a Microsoft Entra ID device registration where the recorded cloud device operating system build is “10.0.19041.928” and the device display name follows the default “DESKTOP-” pattern. This combination is the default device profile that ROADtools (roadtx) uses when registering a device, and it is uncommon for the OS build to match the hardcoded value across an environment of otherwise patched hosts. Adversaries register rogue devices in Entra ID to acquire a Primary Refresh Token (PRT), establish persistence, and obtain trusted, programmatic access to the tenant. Because the OS build is a tool default, this is a high-fidelity but evadable indicator; baseline approved provisioning tooling and device naming conventions before relying on it.

Detection logic

data_stream.dataset:"azure.auditlogs" and event.action:"Add device" and
    azure.auditlogs.properties.target_resources.0.modified_properties.3.new_value:*10.0.19041.928* and
    azure.auditlogs.properties.target_resources.0.modified_properties.4.new_value:*DESKTOP-*

Entra ID Device Registration with Phishing Kit Default OS Build

Description

Identifies a Microsoft Entra ID device registration where the recorded cloud device operating system build is “10.0.19045.2006” and the device display name follows the default “DESKTOP-” pattern. This is the frozen default device profile observed when adversary-in-the-middle (AiTM) phishing kits such as Tycoon2FA and Kali365 register Azure AD-joined devices after capturing a victim session, in order to acquire a Primary Refresh Token (PRT) and establish persistence. The build is hardcoded by the tooling and it is uncommon for the OS build to match this exact value across an environment of otherwise patched hosts, where a current Windows 10 22H2 device reports a far higher “10.0.19045.” value.

Detection logic

data_stream.dataset:"azure.auditlogs" and event.action:"Add device" and
    azure.auditlogs.properties.target_resources.0.modified_properties.3.new_value:*10.0.19045.2006* and
    azure.auditlogs.properties.target_resources.0.modified_properties.4.new_value:*DESKTOP-*