Get fresh insights, pro tips, and thought starters–only the best of posts for you.
A C2 beacon is a recurring communication sent from a compromised device to a command-and-control (C2) server controlled by an attacker. The beacon allows malware or other malicious software to check in with the attacker’s infrastructure, receive instructions, transmit information, or maintain communication with attacker-controlled systems.
C2 beaconing is a common tactic used in cyberattacks because it enables threat actors to remotely manage compromised systems after initial access has been established.
Once a device is compromised, malware may attempt to establish communication with an external C2 server. Rather than maintaining a constant connection, many threats use periodic beaconing to reduce network visibility and avoid detection.
A typical C2 beacon may:
The frequency, timing, and communication method of a beacon can vary depending on the malware family and the attacker’s objectives.
A C2 beacon often indicates that an attacker has established a foothold within a device or network. Once communication is active, threat actors may be able to expand their activities beyond the initial compromise.
| Risk | Potential Impact |
| Remote Command Execution | Execution of attacker-controlled actions |
| Data Exfiltration | Unauthorized transfer of sensitive data |
| Malware Deployment | Installation of additional malicious tools |
| Lateral Movement | Expansion to other systems and accounts |
| Persistence | Continued access to compromised environments |
Because beaconing activity may blend with normal network traffic, early detection is often critical to limiting attacker activity.
Although the terms are related, they refer to different parts of the attack chain.
| C2 Beacon | Command-and-Control Server |
| Communication sent by compromised systems | Infrastructure controlled by attackers |
| Used to check in and exchange information | Used to issue commands and receive data |
| Originates from infected devices | Receives and manages beacon traffic |
| Indicates possible compromise activity | Acts as the attacker’s control platform |
Understanding this distinction helps security teams investigate and contain malicious communications more effectively.
C2 beaconing often originates from compromised endpoints. Maintaining visibility into managed devices and ensuring they remain compliant with organizational security policies are important parts of a broader security strategy.
Hexnode UEM helps IT teams manage and secure endpoints through centralized device management, compliance monitoring, application management, security policy enforcement, and remote troubleshooting capabilities. Combined with security monitoring and threat detection solutions, Hexnode can help organizations maintain oversight of managed devices and support endpoint-related security operations.
Organizations can improve their ability to identify suspicious command-and-control communications by combining endpoint, network, and security monitoring practices.
Key recommendations include:
Effective detection often relies on correlating endpoint and network signals to identify potential compromise activity.
No. While many modern malware families use C2 communications, some threats operate without persistent beaconing.
Yes. Many threat actors use encrypted channels to help conceal command-and-control communications.