Insights

On-Path Attacks: How Interception Works and How to Protect Your Traffic

An on-path attacker intercepts traffic between devices. Learn how attacks work, what HTTPS protects, which warning signs matter, and how to respond.

On-path attacks: how interception works and how to protect your traffic: Ethernet cable with a midspan interception tap, with the doxxnet wordmark.
On this page

An on-path attack happens when an attacker gets into the route between two communicating devices and intercepts, redirects or alters their traffic. You may also hear it called a man-in-the-middle (MITM) attack. Being on the path doesn't automatically let an attacker read encrypted content. Properly validated HTTPS/TLS limits what they can see and change, although some metadata can stay visible.

In short:

  • On the path isn't inside the message. Encryption still protects content when it's validated properly.
  • What leaks: which servers you contact, when and how often.
  • What to do: treat certificate warnings as stop signs, and respond from a connection you trust.

Interception starts with a position in your traffic path

The basic flow is your device → attacker-controlled intermediary → intended service. The intermediary passes your requests and the service's responses along, so the connection keeps working while your traffic goes through the attacker. A rogue hotspot is a simple example: it can give you a working connection without being a safe place to send unprotected information.

A passive on-path attacker watches communication without changing it. An active attacker tries to alter the exchange, for example by redirecting a request or modifying unprotected content. The difference matters because an attack doesn't have to cause a visible failure. Observation alone can threaten your privacy if the traffic exposes something sensitive.

"On-path" describes where the attacker sits: somewhere along the route, not necessarily next to your device. "MITM" usually means the same category of attack. Neither term means the attacker has broken encryption, taken over your account or compromised either end of the connection.

For your privacy, it helps to separate access to the path from access to the message. An attacker may see encrypted traffic without learning what's in it, while plain HTTP can expose everything being exchanged. A phishing page, a compromised account or an infected device isn't by itself evidence of an on-path attacker, even though each of those can also put your information at risk.

Common ways an attacker gets between you and a service

Some techniques create an interception position, and others exploit one that already exists. Rogue Wi-Fi and local-network redirection put traffic under an attacker's control. SSL stripping is different. It tries to keep your side of an intercepted connection unencrypted instead of decrypting a working HTTPS session.

MechanismWhere it actsWhat it tries to defeat
Rogue Wi-FiThe wireless network you joinYour assumption that the access point is a trustworthy route. Attackers can exploit weak wireless security to intercept activity, but controlling a hotspot doesn't by itself defeat validated HTTPS.
ARP spoofingA local network that uses the Address Resolution ProtocolThe local mapping between network addresses and devices. The attacker falsely links their device's address to the gateway's address, so local traffic flows through their device.
DNS spoofingThe lookup that turns a hostname into an addressYour expectation that a lookup leads to the right destination. Manipulated answers can send users to malicious websites, but a redirect alone doesn't give the attacker a valid certificate for the real HTTPS hostname.
SSL strippingThe connection between your device and an intermediaryThe move from an insecure connection to HTTPS. The intermediary uses HTTPS toward the service while serving plain HTTP to you, so your side stays in plaintext.

ARP spoofing is about the next stop on your local network. DNS spoofing is about the address returned for a name. Neither is a universal explanation for interception. A changed DNS answer can be perfectly legitimate, and not every malicious DNS redirect involves an attacker sitting on your existing path.

Session-token theft is a possible result of exposure, not a requirement for getting on the path. A token represents a logged-in session, so an attacker with a usable token may not need your password at all. What matters is whether sensitive traffic or session information became accessible, not just whether an unfamiliar intermediary was there.

What an attacker can see when HTTPS is working

Ordinary HTTP is plaintext. An on-path attacker can read it and may change it. Properly validated HTTPS/TLS protects the content between the two endpoints, as long as those endpoints and their trust settings are intact.

Capturing encrypted packets isn't the same as reading them. Even when encryption holds, an attacker can see which servers you contact, when, and how often. That's the privacy trade-off: what you say may stay confidential while where you go and how often you go there stays visible.

SSL stripping works by keeping HTTPS off your side of the connection. It doesn't decrypt a TLS session that was already established and correctly validated. You might be talking to the intermediary over HTTP while the intermediary talks to the real service over HTTPS. The service's encrypted connection doesn't protect the plaintext leg between you and the attacker.

HSTS limits this downgrade by telling the browser to use HTTPS. It only helps when the browser already knows a policy for that site, either learned earlier or preloaded. A first visit can still be exposed if neither applies. So check the connection you're actually using. Don't assume that because a service supports HTTPS, every visit used it.

Certificate validation is part of this protection, not an obstacle to click through. Accepting a certificate warning can undermine the check that tells your device which service it's talking to. A valid HTTPS connection authenticates the hostname and protects the content. It doesn't show that the website's operator is honest, and it doesn't hide every piece of traffic metadata.

Choose protection for the communication you need to keep private

Match the protection to what you want to keep private and who should receive it. Browsing, private conversations and connections to self-hosted services each have different boundaries. A protected route helps, but it doesn't replace verifying the service or controlling who can use it.

CommunicationRelevant controlWhat it protectsWhat you still need to check
BrowsingHTTPS/TLS with proper certificate verificationContent between your browser and the authenticated serviceThe hostname is the one you meant, validation succeeds and you aren't on an unexpected HTTP connection. HTTPS doesn't make a site honest.
Private messages and callsEnd-to-end encryptionMessage or call content between the participants' endpointsThe participants and devices are the right ones. Content is readable at the endpoints after decryption.
Device-to-service or agent-to-service connectionsAuthenticated, encrypted connections plus access controlsTraffic between the device or agent and its intended serviceThe service identity validates, credentials are protected and permissions fit the task. Network access alone shouldn't authorize every action.

For private services, authentication matters as much as encryption. Digital certificates support secure authentication through PKI, but the connection still has to validate the identity you meant to reach. An encrypted connection to the wrong service doesn't solve your original privacy problem.

A private network or another layer of encryption can protect one communication boundary without protecting everything beyond it. Application authentication and access controls still matter. No transport layer protects data once a compromised endpoint has decrypted it, and no single control stops every kind of interception or exposure.

Multi-factor authentication reduces many account-takeover risks, but it isn't a complete defense against session theft. An intercepted session token can let an attacker impersonate a signed-in user without the password if the application allows the token to be replayed. Protecting active sessions is a separate job from protecting the initial login.

Warning signs are reasons to investigate, not proof

A warning can tell you something is wrong without telling you why. Certificate problems, unexpected plaintext connections and unexplained redirects deserve attention because they can undermine the protection you expected. Pause sensitive activity while you investigate, rather than trying to make the warning go away.

What you seeWhat it tells youWhat to do
Certificate warningCertificate validation failed, for example an expired or untrusted certificate. Interception is only one possible cause.Don't bypass the warning. Check the hostname and retry from a connection you trust.
Unexpected HTTP connectionThe connection has no HTTPS protection. It doesn't tell you whether a downgrade attack happened.Stop entering sensitive information. Use the service's known HTTPS address and confirm validation succeeds.
Redirect or hostname changeYour browser ended up at a different address or name, for a legitimate or malicious reason.Compare the destination with the address you meant to visit. Don't sign in until you understand the change.
Unexpected local ARP mappingThe local address mapping differs from what you expected. A legitimate network change is still possible.If you run the network, compare it with the known gateway configuration. Otherwise contact the administrator.
Changed DNS answerA lookup returned a different destination. Legitimate infrastructure changes can cause this.Check with the service or network administrator before assuming it's malicious.
Network slowdownPerformance changed. Latency alone is weak evidence of interception.Compare with normal behavior and look for other signs before diagnosing an attack from delay alone.

Certificate expiry and configuration mistakes can trigger warnings without any attacker involved. DNS changes and redirects can also be part of ordinary operations. The useful questions are what changed, whether the change was expected, and whether the connection still authenticates the service you meant to reach.

For technical investigation, timing changes are noisy and work best alongside other indicators and a baseline. One slow connection tells you very little. And normal-looking traffic doesn't prove interception is absent, because a passive observer needn't alter anything and a forwarding intermediary can keep everything working.

Respond from a trusted connection

Act promptly if you suspect an on-path attack, but treat containment and diagnosis as two separate steps. You can stop further exposure before you know whether the cause is interception, a service error or a problem with your device.

  1. Stop entering secrets. Pause logins, payments, private messages and other sensitive activity on the affected connection. Don't accept certificate errors to carry on, because that removes an important identity check.
  2. Leave the suspect network. Disconnect and switch to a connection you trust independently. Reconnecting to the same hotspot doesn't give you an independent comparison.
  3. Record what you saw. Note the hostname, the warning or unusual behavior, and the time. Keep the record about your own connection. You don't need to collect anyone else's traffic.
  4. Verify the service through a known address. Use an address you already trust instead of following a suspicious redirect. If certificate validation still fails, stop and contact the service administrator through an established channel.
  5. Protect accounts that may be exposed. From a trusted device and connection, change passwords that may have crossed an unprotected connection and revoke active sessions where the service lets you. Revoking matters because a stolen session token may allow impersonation without another password login.
  6. Review activity and report the problem. Check affected accounts for unfamiliar sessions or actions. Send the hostname, timing and warning details to the account provider or network administrator so they can investigate the right service or network.

If the warning disappears on another network, that points to a difference between the two connections, but it doesn't prove an attack happened. If the warning persists, check your device and the service as well. Go back to sensitive activity only when the connection you intended validates successfully, not just because the page loads again.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.