---
title: Hunt: detect timeroasting by flagging hosts that ask a domain controller to sign NTP replies for a machine account other than their own; packet size alone misleads | ctxsec
url: https://ctxsec.com/items/hunt-huntress-timeroasting-detect-ms-sntp-requests-for-a-rid-other-than-the-senders-machine-account-udp-123-extended-120-byte-authenticator
description: "Timeroasting abuses Microsoft's MS-SNTP extension: without authenticating, anyone can send NTP requests naming an account's RID and get back a MAC derived from that computer or trust account's password, then crack weak ones offline. The targeted accounts never log on, so there are no 4768/4769/4624/4776 events. Huntress reversed the extended 120-byte authenticator (SP800-108 KDF plus HMAC-SHA512) that modern Windows sends by default and released Python and hashcat tooling for it, since hashcat mode 31300 only cracks the legacy 68-byte MD5 form. Defender for Identity didn't flag the unauthenticated sweep in its testing."
status: "research (Huntress, Nov 19, 2026)"
published: 2026-11-19
---

> Timeroasting abuses Microsoft's MS-SNTP extension: without authenticating, anyone can send NTP requests naming an account's RID and get back a MAC derived from that computer or trust account's password, then crack weak ones offline. The targeted accounts never log on, so there are no 4768/4769/4624/4776 events. Huntress reversed the extended 120-byte authenticator (SP800-108 KDF plus HMAC-SHA512) that modern Windows sends by default and released Python and hashcat tooling for it, since hashcat mode 31300 only cracks the legacy 68-byte MD5 form. Defender for Identity didn't flag the unauthenticated sweep in its testing.

[← Threat Hunting](/hunting) · [markdown](/items/hunt-huntress-timeroasting-detect-ms-sntp-requests-for-a-rid-other-than-the-senders-machine-account-udp-123-extended-120-byte-authenticator.md)

research (Huntress, Nov 19, 2026)

2026-11-19 · published here

2026-11-21 3:43 PM ET

### Hunt: detect timeroasting by flagging hosts that ask a domain controller to sign NTP replies for a machine account other than their own; packet size alone misleads

- **Detection:** alert when the RID in an authenticated NTP request (KeyIdentifier at offset 48) isn't the requesting host's own machine account, and on one source requesting many RIDs. Don't alert on 120-byte packets alone; normal Windows clients send them.
- **Telemetry:** UDP/123 traffic to DCs (network sensor or DeviceNetworkEvents); a volumetric count per source is the fallback.
- **Mitigate:** limit UDP/123 on DCs to networks that need it, keep machine-account password rotation on, fix predictable pre-Windows 2000 computer passwords, and roll the AZUREADSSOACC key every 30 days if Seamless SSO is enabled.

Sources: [Huntress: Detecting Timeroasting the Hard Way (Andrew Schwartz, Nov 19, 2026)](https://www.huntress.com/blog/detecting-timeroasting)
