Entra ID Phishing Kit Default OS Build (Entity Analytics)
Identifies the first occurrence of a Microsoft Entra ID device, surfaced through the Entra ID Entity Analytics device inventory, whose host name follows the default "DESKTOP-" pattern and whose operating system build…
Description
Identifies the first occurrence of a Microsoft Entra ID device, surfaced through the Entra ID Entity Analytics device inventory, whose host name follows the default "DESKTOP-" pattern and whose operating system build is "10.0.19045.2006". 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 differs from legitimate hosts: a patched Windows 10 22H2 device reports a far higher "10.0.19045.<revision>" value, so a device frozen at ".2006" with a default name is a high-fidelity, though evadable, indicator.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- event_index
Known benign triggers
- Authorized red team or penetration testing engagements that register devices with this OS profile will appear in the device inventory and match this rule. If this is expected, add exceptions for the specific host names or device IDs.
- Unmanaged or never-patched Windows 10 22H2 hosts may legitimately report the `10.0.19045.2006` build with a default "DESKTOP-" host name. Validate against your device inventory and patch baseline before escalating.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| any.run/malware-trends/kali365/ | 4 |
| any.run/malware-trends/tycoon/ | 12 |
| arcticwolf.com/resources/blog/token-bingo-dont-let-your-code-be-the-winner/ | 7 |
| www.huntress.com/blog/kali365-device-code-phishing-kit | 4 |
| www.ic3.gov/PSA/2026/PSA260521 | 6 |
From the source
- At source
- Open at source
- Upstream identifier
- 47f1d35c-8ee2-43c9-9651-90f840a0630f
- Tagged by the source as
- Data Source: Microsoft Entra IDData Source: Microsoft Entra ID Entity AnalyticsDomain: CloudDomain: IdentityNoise: UnknownPerformance: FastPlatform: Entra IDProfile: RecommendedResources: Investigation GuideRule Type: New TermsTactic: PersistenceThreat: AiTM PhishingThreat: Kali365Threat: Tycoon2FAUse Case: Asset VisibilityUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3