Apollo
Apollo is an implant/agent associated with the Mythic command-and-control framework. In the provided reporting, it is described as an open-source .NET Mythic agent and as the basis for Stealth Falcon’s earlier customized Apollo implants used prior to the group’s newer Horus tooling. Check Point assessed Horus Agent to be an evolution or rewritten, more advanced successor to Stealth Falcon’s customized Apollo implant, with Stealth Falcon (aka FruityArmor) previously using customized Apollo agents in operations spanning roughly 2022–2023. The content does not directly attribute specific standalone Apollo intrusions, but it does state that Stealth Falcon’s later Horus malware replaced earlier customized Apollo agents in espionage activity targeting government and defense entities in the Middle East and Africa, including Turkey, Qatar, Egypt, and Yemen. Additional content notes that defenders published YARA rules for detecting the Mythic C2 framework and its Apollo agent, including a .NET Apollo variant, by matching strings related to C2 communications, agent-specific classes, built-in commands, and internal manager classes. No high-confidence infection vector, standalone Apollo-specific capabilities, or Apollo-specific IOCs beyond those detection-rule references are directly provided in the content.
Hunt this family in your stack
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
Vulnerabilities exploited
1 CVE Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.
Microsoft patched a zero-day vulnerability in its web application framework exploited by an Emirati threat group as part of an espionage campaign in the Middle East and Africa. The flaw, tracked as CVE-2025-33053, is a remote code execution vulnerability in Web Distributed Authoring and Versioning, or WebDAV.
Groups observed using it
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
Named after the Egyptian falcon-headed sky god, Horus Agent represents an evolution from the group’s previously used customized Apollo implant.
Techniques & procedures
2 distinct techniques documented for this family, organized by ATT&CK tactic.
Stealth
1 technique"Horus Agent uses what appears to be a custom OLLVM, leveraging both string encryption and control flow flattening," Check Point said.
Command and Control
1 technique...the latest version of Horus Agent, a custom-built implant designed to operate with the Mythic C2 command-and-control framework.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Mythic C2 agent (Apollo), including a .NET variant; referenced in the context of YARA-based detection via embedded strings/classes/commands.
Open-source Mythic .NET agent that Stealth Falcon previously customized and used; described as having victim fingerprinting and limited command support for stealth and small size.
Previously used customized agent/implant family attributed to Stealth Falcon, referenced as an earlier generation compared to the newer Horus tooling.
A previously used customized implant associated with Stealth Falcon, referenced as the predecessor to Horus Agent.
The version that knows your environment.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.