TOPSpin Security
Blog

Every major incident leaves a trail of lessons for defenders.We read the record so the next alert is not ignored.

Spotting Command-and-Control Beacons in Network Traffic

A wooden cable reel wound with fibre-optic cable
A wooden cable reel wound with fibre-optic cable. Photo: SwarmCheng, CC BY-SA 4.0, via Wikimedia Commons.

Once malware is running inside a network, it needs to talk to its operator. That conversation, known as command and control (often shortened to C2 or CnC), is one of the most reliable ways to find an infection. The malware can hide its files and disguise its processes, but sooner or later it has to send packets out of your network.

What beaconing looks like

Most implants check in on a schedule: every minute, every hour or once a day, asking whether there are new instructions. Developers add random jitter so the timing is not perfectly regular, but over hundreds of connections a pattern still emerges. Compared with human browsing, which comes in bursts during working hours, beacon traffic is steady, small and persistent, including at night and at weekends.

Useful indicators

  • Regular timing. Connections from one host to one destination at near-constant intervals.
  • Rare destinations. Domains that only one or two machines in the whole organisation ever contact.
  • Young domains. Destinations registered days or weeks ago, or with unusual hosting history.
  • DNS oddities. Very long or random-looking subdomains and high volumes of TXT queries can indicate data being smuggled through DNS.
  • Client fingerprints. TLS fingerprinting methods such as JA3 and its successor JA4 can show that a "browser" connection was actually made by a scripting library or malware toolkit.

Architecture beats signatures

Lists of known bad domains and addresses help, but attackers change infrastructure constantly. Design choices last longer. Force outbound web traffic through a proxy that logs it. Allow servers to reach only the destinations they need. Send DNS from all endpoints through resolvers you control and log. These steps make beacons both harder to hide and easier to analyse.

Using decoys to confirm

A beaconing host is a strong lead, not a verdict; plenty of legitimate software phones home on a schedule. A second, independent signal settles it. If the same host has also touched a decoy file share or tried a planted credential, you can act with confidence. That combination of traffic analysis and deception was the core idea behind early decoy network products, and it remains sound today.

The same technique protects consumer platforms. A sportsbook's back office or a casino's payment gateway should talk to a short, known list of partners. A server in that zone that starts calling an unknown domain every sixty seconds deserves immediate attention, whatever the rest of the traffic looks like.

Back to Top