Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
ARP spoofing sends forged Address Resolution Protocol replies on a local network so that traffic meant for the gateway or another host is delivered to the attacker instead.

What Is ARP Spoofing?
ARP spoofing, also called ARP cache poisoning, is an attack on the Address Resolution Protocol in which an attacker on the same local network broadcasts forged replies claiming that another device’s IP address belongs to the attacker’s MAC address. Hosts update their ARP caches accordingly, and from that moment traffic destined for the real device is switched to the attacker instead. MITRE ATT&CK lists it as T1557.002.
The protocol makes no attempt to prevent this. ARP, defined in RFC 826 and unchanged since 1982, is stateless and unauthenticated. A host that receives a reply it never asked for will usually cache it anyway, and a gratuitous ARP announcement is a legitimate feature used by clustering and failover systems. The attack is simply the protocol being used as designed by the wrong party.
Consider a workstation at 192.168.10.50 and a gateway at 192.168.10.1. The attacker, also on that VLAN, sends two streams of forged replies:
Both caches update, and the attacker now sits in the middle of the conversation. With IP forwarding enabled, packets are relayed onward and the user notices nothing beyond a small amount of extra latency. With forwarding disabled, the result is a targeted denial of service. The replies have to be repeated every few seconds, because ARP entries age out, which is one of the things that makes the attack detectable.
Interception on its own is useful, but the value comes from what follows:
Tooling is unremarkable: arpspoof from the dsniff suite, Ettercap, Bettercap, and Responder for the authentication-capture variants. None of it requires privileged access to the switch, only a position on the segment — which is why an unmonitored meeting room socket, a compromised printer, or a rogue access point is enough.
ARP spoofing is noisy if anyone is listening. Signals worth alerting on include a single MAC address claiming several IP addresses, an IP address whose MAC changes repeatedly, a sharp rise in unsolicited ARP replies, and gateway MAC addresses that differ between hosts on the same VLAN. Network detection and response products and Zeek scripts cover this out of the box; arpwatch remains a serviceable option for smaller networks.
ARP spoofing is a routine step in our network security services, precisely because it shows how much an attacker learns from a single unprotected socket.
No. ARP operates only within a single broadcast domain, so the attacker must already have a presence on the same local segment or VLAN as the target. That presence might come from a compromised workstation, an unmanaged device, a wireless network bridged to the wired LAN, or physical access to a socket. Routed traffic between subnets is out of reach.
It protects the confidentiality and integrity of the traffic, which removes most of the value. An attacker in the path still sees destination addresses, SNI values, and traffic volumes, and can drop or delay packets. Protection depends on clients validating certificates properly and on HSTS preventing downgrade, so internal applications with self-signed certificates and trained-to-click users remain at risk.
ARP spoofing poisons the ARP caches of hosts so they send traffic to the wrong MAC address. MAC flooding attacks the switch instead, filling its content addressable memory table so that it fails open and floods frames to every port. The goals overlap, but the defences differ: dynamic ARP inspection addresses the first, port security the second.
On a suspect host, compare the gateway MAC address in the local ARP table against the address seen by other machines on the same VLAN and against the switch’s own table. Duplicates, rapid changes, or one MAC address claiming several IP addresses point to poisoning. For continuous coverage, enable dynamic ARP inspection logging or run a network monitor that alerts on ARP anomalies.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.