What attackers do. Attackers position themselves between two parties, such as a user and a website or two hosts on a network, to intercept or alter traffic. On local networks this can involve poisoning name resolution or ARP; on the internet it includes reverse proxy phishing kits that capture passwords and session cookies. It serves Credential Access and Collection.
How to defend. Disable legacy name resolution protocols such as LLMNR and NetBIOS where not needed, enforce SMB signing and encrypted protocols, and use network access control. Against phishing proxies, use phishing-resistant MFA such as FIDO2, which binds authentication to the real site. Monitor DHCP, ARP and DNS changes on internal networks.
Signs to look for. Look for duplicate or changing MAC to IP mappings, rogue DHCP servers, unexpected name resolution responses, and logins whose session is immediately reused from a different IP. The common gap is assuming MFA stops credential phishing when the kit relays the MFA step as well.