Threat hunting with ThreatDB: detecting C2 beacons by their regularity
A C2 beacon does not stand out through volume but through regularity. If you only check outbound traffic against blocklists, you will see the beacon only after someone else has already reported it.
On Thursday, 12 November 2026, I showed in the webinar “ThreatHunting mit ThreatDB” (held in German) how to start earlier: not with the known indicator, but with the behaviour of the connection itself.
Why blocklists come too late
A blocklist only knows what someone has already seen and reported. A new command-and-control server is not on it on day one. What gives it away is the pattern: the malware calls home at fixed intervals, often with very little data, but with striking regularity.
How ThreatDB works
Every twelve hours, ThreatDB analyses firewall logs as well as Zeek conn.log and dns.log in Elasticsearch using ESQL pipelines. It looks specifically for three anomalies:
- periodic connections to the same destination
- timing jitter that malware uses to disguise its regularity
- direct-IP egress, i.e. outbound connections without a preceding DNS lookup
Enrichment: outside and inside
Every suspicious IP is enriched with VirusTotal, AbuseIPDB and ASN data. The internal side matters just as much: which host opened the connection, is an EDR agent running on it, and did the edge firewall log the connection at all?
The result is a scored review queue with a traceable chain of evidence, plus an allowlist for known legitimate connections and an export for firewall block rules.
What the webinar covered
I demonstrated the pipeline on a demo system with synthetic telemetry so that every step remained traceable. We also discussed the limits: where beacon detection on metadata level holds up, where it produces false positives, and what a one-month pilot in your own Elasticsearch cluster actually delivers.
Who ThreatDB is for
For SOC leads, CISOs and network teams who already run Zeek and Elastic or are evaluating them. And for organisations that only have a firewall: the analysis also works remotely.
Conclusion
Relying on blocklists alone means reacting to what others have already discovered. The regularity of a beacon, by contrast, is a signal that sits in your own logs and becomes visible earlier. How we proactively search for hidden attackers is described under threat hunting. Upcoming sessions are listed on our webinars page.



