Windows Event ID 4649: A replay attack was detected
Written when a domain controller detects a Kerberos replay (a resend of an identical request) and returns KRB_AP_ERR_REPEAT. It can mean an attack or a network fault.
Overview
The subcategory is Audit Other Logon/Logoff Events. It is generated on a domain controller (the server that governs network authentication). The DC caches information from recently received tickets; if the server name, client name, time, and microsecond fields match a recent entry, it treats it as a replay and returns KRB_AP_ERR_REPEAT (RFC 1510). It requires an Active Directory domain controller.
How it is triggered
- When an identical authentication request (Authenticator) arrives twice.
- A non-attack cause is a misconfigured network device between client and server that resends the same packets repeatedly.
Security review points
- It can be a sign of a
replay attack (capturing legitimate authentication data and resending it as-is to get through authentication). If it occurs, raising an alert and investigating the cause is recommended. - That said, it often appears due to network device configuration or routing problems. Separate attack from device-induced causes using the origin (
Workstation Name, the clients/servers involved).
Notes for log review
- One-off or sporadic occurrences are likely network-induced. Repetition on a specific path or device suggests a configuration problem.
- If it concentrates on a particular account or service, prioritize the possibility of an attack and scrutinize it together with related Kerberos events (4768 / 4769).
MITRE ATT&CK mapping
No technique maps directly. Resending stolen authentication data is close to T1550.003 Pass the Ticket, but network equipment also triggers it, so separate the causes by source.
Mapping as of ATT&CK v19.2. To search by technique, see the ATT&CK reverse lookup.
Detection rules
SigmaHQ has 1 public detection rule that uses this event ID as a condition.
| Rule | Type | Severity |
|---|---|---|
| Replay Attack Detected | Sigma | High |
Rules are collected from SigmaHQ r2026-07-01 and from Azure-Sentinel as of 2026-10-09, limited to those whose conditions include this event ID. Sentinel rules are limited to those that query the SecurityEvent or WindowsEvent table. “Threat-specific” rules target a particular threat group or malware, and “needs setup” rules require values for your environment. Severity is the value each rule’s author assigned.
Key fields
| Field | Meaning |
|---|---|
Credentials Which Were Replayed\Account Name | The account of the replayed credentials |
Workstation Name | The originating workstation name |
Request Type / Authentication Package | The request type and authentication method |