An on-path attack is a network threat where an attacker secretly sits between two parties and watches, changes, or redirects their traffic. Think of a user logging in to a banking site while a criminal silently captures session cookies, DNS replies, or credentials. The damage can get expensive fast: IBM reported the global average cost of a data breach reached $4.88 million in 2024 [source: IBM].
TLDR: An on-path attack happens when an attacker gets between a user and a service, then spies on or changes the data passing through. For example, on public Wi Fi, an attacker could fake a login page and steal passwords from anyone who connects. In a small office with 80 devices, even one poisoned router or spoofed DNS response can expose dozens of accounts in minutes. Wireshark, Burp Suite, and related tools help spot odd traffic, broken encryption, strange certificates, and suspicious redirects.

What an on-path attack looks like
An on-path attack used to be called a man in the middle attack. The name changed, but the idea is the same. The attacker places themselves in the communication path. The user thinks they are talking to a real website. The website thinks it is talking to the real user. Meanwhile, the attacker can observe the conversation.
Sometimes the attacker only listens. That is bad enough. Other times, they change traffic in transit. They may downgrade HTTPS, inject malicious scripts, alter payment details, or redirect users to fake login pages. It drives me crazy that one weak router password can make this possible for an entire office.
Common ways attackers get in the path
- ARP spoofing: The attacker tricks devices on a local network into sending traffic through their machine.
- DNS spoofing: The user types a real domain, but the attacker sends them to a fake address.
- Evil twin Wi Fi: A fake hotspot copies the name of a trusted network.
- SSL stripping: The attacker tries to force traffic from HTTPS down to HTTP.
- Proxy abuse: Traffic is sent through an attacker controlled proxy without the user noticing.
How Wireshark helps detect the problem
Wireshark is one of the best tools for seeing what is actually moving across a network. It captures packets and lets analysts inspect protocols, addresses, ports, handshakes, and payloads where allowed. It is not magic. You still need to know what normal traffic looks like. But it gives you the raw evidence.
With Wireshark, teams can look for warning signs such as:
- Duplicate IP addresses on the same network.
- Odd ARP replies claiming to be the gateway.
- HTTP traffic where HTTPS should be used.
- Unexpected DNS replies from unknown hosts.
- TLS certificate errors or strange handshake behavior.
The catch is that packet captures get noisy fast. A five minute capture on a busy office network can create thousands of packets. Expect to waste time filtering at first. Good filters, such as arp, dns, http, and tls, make the work much less painful.
How Burp Suite helps test web traffic
Burp Suite is built for web security testing. It works as a proxy between the browser and the target application. Security teams use it to inspect requests, edit parameters, test authentication, and check how a site handles sessions.
For on-path risk, Burp Suite is useful because it shows how a web app behaves when traffic is intercepted. Can session cookies be stolen? Are they marked Secure and HttpOnly? Does the site enforce HTTPS? Does it accept weak redirects? These questions matter.
Burp also helps teams test certificate handling, header settings, and login flows. If a web app leaks tokens in URLs or sends sensitive data over plain HTTP, Burp will make that painfully obvious.
Other tools that help
- Zeek: Watches network traffic and creates useful logs for security teams.
- Suricata: Detects known attack patterns and suspicious traffic.
- Ettercap: Often used in labs to simulate on-path attacks.
- Bettercap: Useful for controlled testing of network weaknesses.
- Nmap: Finds hosts, open ports, and services that should not be exposed.
These tools are strongest when used together. Wireshark shows packet detail. Burp Suite shows web behavior. Zeek and Suricata help monitor at scale. Nmap helps find risky devices before attackers do.
How to reduce the risk
You cannot stop every attacker by installing one tool. You need good habits too. Use HTTPS everywhere. Turn on HSTS for websites. Avoid open Wi Fi for sensitive work. Use a trusted VPN when needed. Keep routers patched. Change default passwords. Segment guest networks from business systems.
For companies, certificate monitoring and DNS logging are worth the effort. So is user training. People should know that a browser warning is not a decoration. It means something is wrong.

Final thoughts
An on-path attack is dangerous because it hides in a place users rarely check: the space between sender and receiver. The victim may see a normal website, a normal login page, and a normal connection icon. Underneath, traffic may be watched or changed.
Wireshark, Burp Suite, and other security tools help turn suspicion into proof. They show what is happening on the wire and inside web requests. That visibility matters. Without it, you are guessing. With it, you can spot the threat, fix weak points, and stop a quiet attack before it becomes a very loud incident.