CyberKit

BGP Hijacking

Also called route hijacking, prefix hijacking.

Falsely announcing IP routes to divert or intercept traffic.

What it is

An attack that abuses the trust-based Border Gateway Protocol by announcing IP address ranges the attacker does not own, causing other networks to route that traffic to them. The diverted traffic can be dropped, inspected, or relayed onward.

Why it matters

Route hijacks can silently reroute large volumes of internet traffic for interception or denial, and the resulting routing anomalies are a key signal when investigating sudden, unexplained traffic detours.

In practice

Tracing a brief but suspicious detour of an organization's traffic to a foreign network that had announced its prefixes without authorization.

What to look for

  • Route announcements for your prefixes from unexpected networks.
  • Traffic paths that suddenly change.
  • Certificate requests issued during the hijack window.

Common mistake

Thinking it is only an ISP problem. Monitor your prefixes and use RPKI where you can.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Wireshark Open source

    Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.

  • Zeek Open source

    Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.

  • Suricata Open source

    An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.

  • Arkime Open source

    Indexes full packet capture at scale so you can search and pull sessions later. Our notes.

Read next

Sources