DKDKCISSP
VulnerabilitiesINCIDENT

Detecting Timeroasting the Hard Way

A new detection method for timeroasting has been developed, focusing on monitoring UDP traffic to identify potential password vulnerabilities in Windows systems.

DKCISSP News Desk19 Nov 2026, 7:30 pm2 min read
Detecting Timeroasting the Hard Way
Image courtesy of Huntress. Original report

Researchers have disclosed a new approach to detect timeroasting, a technique that allows attackers to exploit password vulnerabilities in Windows systems by collecting password data for accounts without authentication. This method is significant as it targets weaknesses in the protocol that many existing detection methods overlook.

Timeroasting enables unauthenticated attackers to gather password data for computer and trust accounts, allowing them to attempt offline cracking of weak passwords. The technique exploits Microsoft's proprietary NTP authentication extension, known as MS-SNTP. Unlike traditional attacks that require user authentication, timeroasting allows attackers to request a password-derived MAC from a domain controller simply by identifying the account's Relative Identifier (RID). This capability makes it crucial for organizations to enhance their detection methods against such threats.

The detection process involves monitoring UDP port 123 traffic to domain controllers. An important finding from recent testing is that existing detection methods, such as Microsoft Defender for Identity, did not catch the sweeps associated with timeroasting attempts. The researchers found that alerting on requests for a machine account signature other than the host's own could enhance detection capabilities. This approach relies on understanding the protocol's specifications and the binary that implements it, rather than solely depending on vendor feeds or breach reports.

Timeroasting is a technique that relies on the Network Time Protocol (NTP) to exploit weaknesses in the authentication process. In this attack, a domain client sends a request to a domain controller for a time response, naming an account by its RID. The controller responds with a MAC computed using the account's password-derived key. This process does not require prior authentication, allowing attackers to sweep RIDs and collect MACs for offline cracking. Understanding the two formats of authenticators—legacy and extended—is crucial for effective detection.

The timeroasting attack primarily affects accounts with weak or unchanged passwords. As these accounts are often not monitored closely, they remain at risk. The extended authenticator format, which has been in use for years, complicates detection efforts as it does not have public cracking support. Organizations must be aware of the distinction between the two formats, as failure to recognize them could lead to misinterpretation of account safety.

The timeline of events surrounding timeroasting has not been explicitly detailed in the available research. However, it is known that the attack has evolved alongside updates to Windows systems and the introduction of the extended authenticator format. The ongoing research into timeroasting reflects a growing need for more sophisticated detection methods that can adapt to the changing landscape of cybersecurity threats.

What remains unclear is the full extent of timeroasting's impact on various organizations and how many accounts may be vulnerable. As this technique becomes more recognized, security teams need to monitor developments closely and adjust their defenses accordingly.

What security teams should do

  • Monitor UDP port 123 traffic to domain controllers.
  • Ensure detection tools are updated to handle both legacy and extended authenticator formats.
DKCISSP VIEWOur take, not reported fact

What it meansNew detection methods for timeroasting focus on monitoring network traffic to identify vulnerabilities in password management.

Ask your IT team this weekHow are we currently monitoring UDP port 123 traffic to our domain controllers?Do we have visibility into the authentication methods used by our accounts?

DecisionThe IT team will implement enhanced monitoring for UDP port 123 traffic, and security will verify its effectiveness.

MORE IN VULNERABILITIES

More cybersecurity reporting

Ruby Ships Fixes for 7 Flaws, Including Critical Ruby2Shell, Said to Hit Default Rails Apps Pre-Auth20 Nov 2026, 12:23 pmChina-Linked Hackers Exploited VMware ESX Zero-Day to Reduce Audit Trail Visibility20 Nov 2026, 12:05 pmNew Unpatched Windows 0-Day FastUnlock Lets Someone Holding a Locked PC Run Programs on It20 Nov 2026, 11:00 amCritical VMware vCenter Zero-Day Flaw Lets Network Attackers Bypass Authentication20 Nov 2026, 7:57 am