Has used ARP spoofing to redirect a compromised machine to an actor-controlled website.1
ARP Cache Poisoning T1557.002
- Tactics
- Credential Access, Collection
- Platforms
- Linux, Windows, macOS
- Version
- 1.1
- Created
- 15 October 2020
- Last modified
- 24 October 2025
- Contributor
- Jon Sternstein, Stern Security
Adversaries may poison Address Resolution Protocol (ARP) caches to position themselves between the communication of two or more networked devices. This activity may be used to enable follow-on behaviors such as Network Sniffing or Transmitted Data Manipulation.
ARP Cache Poisoning MITRE reference T1557.002
2 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
All 2 groups for this technique
Offense vs defense T1557.002
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
ARP Cache Poisoning detection strategy DET0387
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detect ARP Cache Poisoning Across Linux, Windows, and macOS
AN1091 · Windows
Detects anomalous ARP traffic or cache modifications on Windows endpoints that indicate ARP poisoning. Behavioral focus is on multiple IP addresses resolving to a single MAC, or unsolicited ARP replies from unauthorized devices.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Traffic FlowDC0078 | WinEventLog:Security | ARP cache modification attempts observed through event tracing or security baselines |
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TrustedGatewayMAC | Expected MAC address for default gateways; deviations may indicate poisoning. |
| TimeWindow | Correlation interval for repeated unsolicited ARP replies. |
AN1092 · Linux
Detects suspicious gratuitous ARP responses or inconsistent IP-to-MAC mappings using auditd and packet capture. Behavioral focus is on unsolicited replies overriding legitimate ARP ownership.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Traffic FlowDC0078 | NSM:Flow | Gratuitous ARP replies with mismatched IP-MAC binding |
| Network Traffic ContentDC0085 | auditd:SYSCALL | setsockopt, ioctl modifying ARP entries |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| AllowedARPUpdates | Expected legitimate IP-to-MAC updates for servers or virtual routers. |
| AlertThreshold | Number of anomalous ARP packets per second before triggering detection. |
AN1093 · macOS
Detects anomalous ARP cache changes and unsolicited ARP broadcasts using unified logs and packet capture. Behavioral detection includes multiple IP addresses mapped to the same MAC address and repeated gratuitous ARP traffic.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Traffic FlowDC0078 | macos:unifiedlog | ARP table updates inconsistent with expected gateway or DHCP lease assignments |
| Network Traffic ContentDC0085 | NSM:Flow | Excessive gratuitous ARP replies on local subnet |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| GatewayMACBaseline | Known MAC addresses for gateways or DHCP servers; used to detect spoofed ARP entries. |
| CorrelationDepth | How many ARP inconsistencies to tolerate before escalating detection. |
Consider disabling updating the ARP cache on gratuitous ARP replies.
Ensure that all wired and/or wireless traffic is encrypted appropriately. Use best practices for authentication protocols, such as Kerberos, and ensure web traffic that may contain credentials is protected by SSL/TLS.
Consider enabling DHCP Snooping and Dynamic ARP Inspection on switches to create mappings between IP addresses requested via DHCP and ARP tables and tie the values to a port on the switch that may block bogus traffic.
Create static ARP entries for networked devices. Implementing static ARP entries may be infeasible for large networks.
Network intrusion detection and prevention systems that can identify traffic patterns indicative of AiTM activity can be used to mitigate activity at the network level.
Train users to be suspicious about certificate errors. Adversaries may use their own certificates in an attempt to intercept HTTPS traffic. Certificate errors may arise when the application’s certificate does not match the one expected by the host.