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 Overlord C2? The Threat-Feed Label Explained

A C2 family name you will meet in threat feeds, with little public documentation behind it. What the label means and how to handle hits.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
5 min read
Type
Threat-feed label

In short

Overlord C2 is a label that threat-intelligence feeds apply to a family of command-and-control servers. It groups listeners that share traits such as generated TLS certificates and common ports. Public documentation does not tie the label to one well-known tool, so a match is a lead that needs a second signal before you block.

Key takeaways

What it is
A threat-feed label for a family of C2 servers, not a documented product with a public manual. Treat it as a cluster name.
How it shows up
Listeners on ports such as 5173, 443 and 8443, some with generated certificates whose subjects end in .invalid.
Why it matters
A few Overlord servers are real C2. Many more are look-alikes, so blocking every match risks cutting off harmless services.
What Odin Research saw
107 Overlord endpoints on 94 hosts in Monograph 19, with 4 confirmed C2 listeners and four multi-port hubs.
What to do first
Block only confirmed listeners, and add the generated certificate pattern to your TLS hunting.

What is Overlord C2?

Overlord C2 is a name that threat-intelligence feeds give to a family of command-and-control servers. The label groups listeners that share traits, such as generated TLS certificates and common ports. It is a cluster name. It does not point to one well-documented product or to a named threat actor.

Odin Research met the label in Monograph 19, which studied six evasive command-and-control frameworks. Overlord was the fourth largest, after Brute Ratel C4, Cobalt Strike and DarkSword.

Labels like this are common in threat feeds. They let a feed say "these servers look alike" before anyone knows who runs them. Monograph 19 handles DarkSword the same way: as a feed label, not an actor.

The practical point: an Overlord hit tells you a server matched a pattern. It does not tell you what software runs there or who controls it.

How Overlord C2 servers look

Monograph 19 describes three recurring traits.

  1. Generated certificates. Confirmed single-port servers present TLS certificates with machine-generated subjects of the form host-<16 hex characters>.invalid. RFC 2606 reserves the .invalid top-level domain for names that are sure to be invalid, so a real public website would not use it.
  2. A dominant port. Almost half the endpoints (51 of 107) listened on port 5173. Others used 443, 8443 and, in three cases, 1080 for SOCKS proxying.
  3. Small hubs. Some operators stack three or four Overlord listeners on one server, often on 80, 443 and 8443.

Two of these traits need care. Port 5173 is also the default port of the Vite web development server, according to Vite's documentation. Many harmless developer machines listen there. Shared TLS fingerprints such as JARM group servers built the same way, but Salesforce, which created JARM, warns that matches include legitimate servers.

The certificate pattern is the stronger signal. Monograph 19 counted 11 Overlord endpoints on ports 8443 and 9000 that share one JARM value, including both published C2 servers.

Where the Overlord C2 name comes from

The name is ambiguous, which is one reason to treat it as a label. A public GitHub project called Overlord, published by qsecure-labs, automates red-team infrastructure. Its README describes a Python console that builds C2, email and phishing servers on AWS and DigitalOcean. It is MIT-licensed and builds on the Red-Baron Terraform project.

Monograph 19 does not link the Overlord feed label to that project. Nothing in the report ties the observed servers to qsecure-labs or to any other named author. Do not assume an Overlord hit means that tool is running.

Why Overlord C2 matters to defenders

Some Overlord servers are real, working C2 listeners. Monograph 19 groups Overlord with Brute Ratel C4, DarkSword, Mythic and Havoc as an evasive implant fleet that calls home over HTTPS. Confirmed listeners belong on block lists.

The bigger risk is the reverse. If a security operations team pushes every Overlord match into a firewall, it will also block developer servers, generic web services and reassigned home broadband addresses. Odin Research's broader work on false positives shows how often single-trait C2 rules hit harmless servers.

Overlord also appears next to other tools. Monograph 19 found Overlord on the same host as Sliver in at least one case, on a host not published in the report. Shared hosting with a second offensive tool is a stronger lead than either signal alone.

What Odin Research observed

Monograph 19 covered a two-week window ending 18 November 2026.

  • 107 endpoints on 94 hosts. Four are confirmed C2 listeners. 31 are suspected, and 71 are candidates or open directories. One sits on a subscriber telecom network.
  • Hosting. Germany (42) and the United States (25) lead. Providers include Blatant Technologies (16), OVH (13), EggyWall.org (8), AWS (8), Hetzner (7) and Private Layer (6).
  • Two published C2 servers. Both use the generated .invalid certificate pattern, one in the Netherlands and one in the United States. Their addresses are in the report's Indicators tab.
  • Four hubs. Two three-port hubs on Private Layer in Switzerland reuse one helper certificate, with two confirmed sockets each. A four-port hub on OVH in Germany stays suspected.
  • Four still suspected. These lack the family fingerprint or a known certificate subject, so they stay off block lists.

How to detect Overlord C2

  • Hunt the certificate pattern. Alert on outbound TLS sessions where the server certificate subject matches host-<16 hex>.invalid.
  • Pair signals. Combine the certificate check with a JARM match and with endpoint data on which process opened the connection.
  • Do not hunt on port 5173 alone. It is too common on developer machines to mean much without another signal.
  • Watch your own perimeter. External attack surface management helps you confirm you are not hosting a matching listener yourself.

Monograph 19 publishes a Suricata signature (SID 9519004) for Overlord's generated server certificates. It is in the report and in the Defense Kit. The certificate rule needs TLS certificate subject inspection on server handshakes.

How to respond to an Overlord C2 hit

  1. Check the evidence type. A certificate match on a dedicated cloud server is stronger than a port match on a broadband line.
  2. Block confirmed listeners. Use the published indicators, and re-check cloud addresses after a few weeks, since they get reassigned.
  3. Watchlist the rest. Keep suspected and candidate hits on time-limited watchlists.
  4. Investigate internal contacts. If an internal host talked to a confirmed listener, examine that host for an implant and for web-protocol C2 traffic.

Overlord C2 compared with other feed-labeled C2 families

FamilyWhat the name meansEndpoints (Monograph 19)ConfirmedMain ports
Overlord C2Feed label for a C2 server family10745173, 443, 8443
DarkSwordFeed label for multi-port TLS and HTTP C234610443, 8888, 80
HavocOpen-source C2 framework250443, 8443
Brute Ratel C4Commercial red-team framework6904Many VPN-exit look-alikes

Frequently asked questions about Overlord C2

What is Overlord C2?

Overlord C2 is a label that threat-intelligence feeds apply to a family of command-and-control servers that share traits such as generated TLS certificates and common ports. It is a cluster name, not a documented product.

Is Overlord malware?

The label describes servers, not a file. Some Overlord servers are confirmed C2 listeners. Others are look-alikes. Treat a match as a lead until a second signal confirms hostile use.

Is Overlord C2 the same as the qsecure-labs Overlord project?

Not as far as public evidence shows. qsecure-labs publishes an open-source tool called Overlord that automates red-team infrastructure, but Odin Research found nothing linking the feed label to it.

Who uses Overlord C2?

No public reporting attributes the label to a named threat actor. Odin Research observed the servers mostly on cloud and hosting providers in Germany and the United States.

Why do so many Overlord hits use port 5173?

Odin Research saw 51 of 107 endpoints on port 5173. That port is also the default for the Vite web development server, so a port match alone is weak evidence.

How do I detect Overlord C2?

Hunt for server certificates with subjects of the form host-[16 hex characters].invalid and pair them with TLS fingerprints and endpoint data. Odin Research publishes a Suricata signature for the pattern in its Defense Kit.

Should I block every Overlord C2 address?

No. Block confirmed listeners only. In Monograph 19, 4 of 107 Overlord endpoints were confirmed; the rest belong on time-limited watchlists.

Sources

  1. qsecure-labs, Overlord: Red Teaming Infrastructure Automation, GitHub. github.com/qsecure-labs/overlord (checked 21 November 2026)
  2. Vite documentation, Server Options (server.port). vite.dev/config/server-options (checked 21 November 2026)
  3. IETF, RFC 2606, Reserved Top Level DNS Names. datatracker.ietf.org/doc/html/rfc2606 (checked 21 November 2026)
  4. Salesforce Engineering, "Easily Identify Malicious Servers on the Internet with JARM". engineering.salesforce.com/easily-identify-malicious-servers-on-the-internet-with-jarm-e095edac525a/ (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