HavoX
Techniques & procedures
10 distinct techniques documented for this family, organized by ATT&CK tactic.
Resource Development
1 technique
Resource Development
Operators utilized Cloudflare Workers for XaocMail, Phantom53, and Havoc deployments.
Initial Access
1 technique
Initial Access
Initial Access T1566 Phishing Implant delivered as .pyw; delivery via http8123.log
Execution
1 technique
Execution
HavoX : communication chiffrée avec les machines infectées, exécution de commandes via scripts Python cachés
Persistence
2 techniques
Persistence
Phantom53 watcher launches Havoc demon if the beacon receives the CMD_WAKE command.
Persistence T1547.001 Registry Run Keys HavoX AppData\Roaming persistence path
Privilege Escalation
2 techniques
Privilege Escalation
Phantom53 watcher launches Havoc demon if the beacon receives the CMD_WAKE command.
Persistence T1547.001 Registry Run Keys HavoX AppData\Roaming persistence path
Stealth
2 techniques
Stealth
Defense Evasion T1027 Obfuscated Files .pyw execution via pythonw.exe (windowless)
It then uses a custom reflective loader for memory-only execution.
Command and Control
3 techniques
Command and Control
Command and Control T1071.001 Web Protocols HavoX uvicorn ASGI WebSocket C2 on :8000
all victim traffic hidden behind 12 Cloudflare Workers domains and three parallel C2 frameworks (HavoX, Phantom53, Krint bridge) running on a single Netherlands VPS.
Each agent utilizes a unique AES-256 encryption key to secure its respective communication channel.
Observables
24 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.