Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Threat groups and feed labels

What Is Daybreak C2? The JA4X Heuristic and the MySQL Problem

The biggest C2 label in Odin's feed data, and mostly MySQL: how the heuristic works and how to separate real servers from databases.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
6 min read
Type
Detection heuristic

In short

Daybreak C2 is a command-and-control family label in public threat feeds, detected with a JA4X TLS certificate heuristic. The heuristic also matches the self-signed certificates MySQL generates at startup. In Odin Research's data, 94.5% of actionable Daybreak rows were ordinary MySQL servers on port 3306, so defenders should verify before blocking.

Key takeaways

What it is
A C2 family label in threat feeds, found with a JA4X certificate fingerprint rather than a documented open-source project.
How it works
JA4X fingerprints TLS certificates. MySQL's auto-generated certificates match the Daybreak value, so the heuristic flags databases.
Why it matters
Raw Daybreak indicators fed into block jobs cut off legitimate databases and bury the few real C2 servers.
What Odin Research saw
1,592 MySQL servers labelled confirmed Daybreak C2; only 71 endpoints, none on port 3306, held up as real Daybreak C2.
What to do first
Remove port-3306 Daybreak indicators from automatic blocking and require a second, independent signal.

What is Daybreak C2?

Daybreak C2 is a command-and-control (C2) family label carried by public threat feeds, paired with a JA4X certificate heuristic for spotting its servers. The heuristic also matches the self-signed certificates MySQL creates for itself at startup. As a result, most Daybreak hits on port 3306 are ordinary databases, not attacker servers.

Public documentation of the Daybreak framework itself is thin. Odin Research did not find a vendor or project write-up that describes its code. This page therefore focuses on what defenders actually meet: the Daybreak label in their threat feeds, and how to tell a real Daybreak server from a database.

That matters because Daybreak can top a raw C2 ranking. In Odin's data it was the single largest C2 label by volume, and the single largest source of false alarms.

How Daybreak C2 detection works

Daybreak hits come from TLS certificate fingerprinting. JA4X is the X.509 certificate fingerprint in FoxIO's JA4+ suite. Like other JA4+ fingerprints it uses an a_b_c format. FoxIO publishes JA4X under the FoxIO License 1.1, which allows internal business use but needs an OEM license for resale.

A certificate fingerprint is useful against C2 tools that generate their certificates the same way every time. The catch is that unrelated software that also generates certificates automatically can end up with the same fingerprint.

That is what happens with MySQL. The false positive comes from three ordinary behaviors, all documented by MySQL:

  1. Automatic certificates. With auto_generate_certs, enabled by default in OpenSSL builds, MySQL creates its own CA, server and client certificates at startup when none exist.
  2. Predictable names. The server certificate is named MySQL_Server_<version>_Auto_Generated_Server_Certificate, signed by a self-signed MySQL CA and valid for ten years.
  3. A server that speaks first. Odin's Monograph 13 notes that a MySQL server sends a fixed greeting first. A loose C2 rule can read a short binary greeting plus a self-signed certificate as a beacon.

Odin's Monograph 07 found that the Daybreak JA4X value matches the structure of auto-generated MySQL 8.x certificates.

Why the Daybreak C2 label matters to defenders

A feed that labels databases as C2 does real damage when it drives automatic blocking. Block jobs can cut off partner databases, cloud services or your own replicas. Analysts lose trust in the feed. Real C2 hides in the noise.

Daybreak is a clear example of a wider problem. Single-trait rules, such as one certificate shape or one port, collide with legitimate software at internet scale. Read more in our page on the Pyramid of Pain, which explains why low-level indicators are both cheap and brittle.

What Odin Research observed

  • Largest label, mostly MySQL. In Monograph 02, Daybreak topped the raw C2 ranking with 1,701 records. Of these, 1,592 (93.6%) sat on TCP 3306 and carried 1,590 auto-generated MySQL certificates and 2 ProxySQL certificates. MySQL 5.7.44 and 8.0.45 led the versions.
  • Few second signals on databases. Monograph 02 examined 59 Daybreak hosts. Another C2 label appeared on another port of 26.7% of non-database candidates (4 of 15) but only 8.0% of port-3306 hosts (2 of 25). Of those 25 database hosts, 21 showed nothing else.
  • Other ports collide too. Daybreak records on ports 1500 and 1501 overlap with a hosting control panel, so they also need an application-layer check.
  • 94.5% false positives. Monograph 13 found 1,592 MySQL servers labelled confirmed Daybreak C2, 76.5% of all 2,081 C2 collisions in that study. Among 1,684 actionable Daybreak rows, 94.5% were MySQL. Only 71 endpoints, none on port 3306, held up as real Daybreak C2, plus 17 on dynamic ISP lines.
  • The real signal sits next door. In Monograph 07, two Sliver servers showed a MySQL certificate on 3306 and the real Sliver operator certificate on port 31337. The Sliver port, not the database, was the evidence.

How to tell real Daybreak C2 from MySQL

  • Read the certificate name. A subject that starts with MySQL_Server_ and ends with Auto_Generated_Server_Certificate is a database default.
  • Check the protocol. If the port answers with a MySQL greeting, treat the hit as a database until other evidence appears.
  • Look for a second signal. Another C2 family on a different port of the same host, a known C2 certificate or C2-specific HTTP traffic is far stronger than the JA4X match.
  • Hunt the other direction. Workstations that connect to public port 3306 are unusual whatever the label says.

Monograph 13 publishes a Suricata rule set with Daybreak signatures and a MySQL guardrail that keeps port-3306 handshakes out of C2 alerts. It adds a YARA rule set, a KQL query that drops the known collision patterns, and a Sigma rule that fires when an automated job tries to block a port-3306 Daybreak indicator. Monograph 02 adds Suricata and Sigma rules for non-MySQL certificates on 3306 and outbound connections to public 3306. All are in the Defense Kit.

How to handle Daybreak C2 alerts

  1. Pull port-3306 Daybreak indicators out of block jobs today. Keep them for hunting only.
  2. Demand a second signal before blocking any Daybreak address on other ports, and re-check addresses on dynamic ISP lines often.
  3. Keep your own MySQL off the internet. An exposed database is a risk in its own right. See how to defend against misconfigurations and EASM 101.
  4. Replace default certificates. MySQL's own documentation warns that its self-signed certificates may not be very secure and recommends a registered certificate authority.
  5. Score your feeds. Track how many feed indicators survive verification. Our threat intelligence evaluation checklist helps.

Daybreak C2 compared with other feed collisions

Feed labelWhat it collided withVolume in Monograph 13Safe check
DaybreakMySQL servers with auto-generated certificates on 33061,592 hostsCertificate name and MySQL greeting
InteractshAWS load balancers356 hostsDo not act on a TLS fingerprint alone
ezXSSPHP 8.5 web servers127 hostsRequire more than a server header
EmotetAutomaker mTLS gateways6 gatewaysIgnore HTTP 400 alone; check the partner hostname

See also our JARM page for a related server-side TLS fingerprint and its limits.

Frequently asked questions about Daybreak C2

What is Daybreak C2?

Daybreak is a command-and-control family label used in threat feeds, detected with a JA4X certificate heuristic. The same heuristic matches MySQL's auto-generated certificates, so most port-3306 Daybreak hits are databases.

Is Daybreak malware?

The label is meant to mark C2 servers. In Odin Research's data, though, 94.5% of actionable Daybreak rows were plain MySQL servers. Only 71 endpoints, none on port 3306, held up as real Daybreak C2.

Why does Daybreak flag MySQL servers?

MySQL creates its own self-signed certificates at startup and speaks first with a fixed greeting. The Daybreak JA4X value matches the structure of those auto-generated MySQL 8.x certificates.

Should I block Daybreak IP addresses?

Not on port 3306. Remove those indicators from automatic block jobs. Block a Daybreak address on another port only when a second, independent C2 signal supports it.

What is JA4X?

JA4X is FoxIO's X.509 TLS certificate fingerprint, part of the JA4+ suite. It is licensed under the FoxIO License 1.1, which needs an OEM license for commercial resale.

How do I recognize a MySQL auto-generated certificate?

Its subject follows the pattern MySQL_Server_<version>_Auto_Generated_Server_Certificate, it is signed by a self-signed MySQL CA and it is valid for ten years from generation.

Where can I get rules that avoid the Daybreak false positive?

Odin Research's Monograph 13 publishes a Suricata rule set with a MySQL guardrail, plus YARA, KQL and Sigma rules. They are in the Odin Defense Kit.

Sources

  1. FoxIO, JA4+ network fingerprinting repository, GitHub. github.com/FoxIO-LLC/ja4 (checked 21 November 2026)
  2. MySQL 8.0 Reference Manual, Creating SSL and RSA Certificates and Keys using MySQL. dev.mysql.com/doc/refman/8.0/en/creating-ssl-rsa-files-using-mysql.html (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit