Skip to main content
Mallory
MalwareUsed by 1 actor

xCaon

xCaon is a previously undocumented malware family associated with the IndigoZebra espionage activity. Reporting cited in the content links xCaon to campaigns targeting political entities in Kyrgyzstan and Uzbekistan, and Kaspersky’s 2017 reporting associated the broader operation with malware including Meterpreter, Poison Ivy RAT, xDown, and xCaon. Check Point identified about 30 xCaon samples, with the earliest dating back to 2014.

High-confidence behaviors described in the content indicate that xCaon used HTTP for command-and-control communications and Base64 to encode its C2 traffic. Data sent to the C2 server was also encrypted with an XOR key. The malware can upload files from victim machines. It performs host discovery by retrieving network adapter information via the Windows GetAdapterInfo() API, and it checks for the presence of Kaspersky antivirus software on the infected system.

The content further notes that xCaon was linked by Check Point to the IndigoZebra threat actor based on similarities with BoxCaon, a related backdoor used in espionage operations against the Afghan government. Only the directly stated capabilities for xCaon are included here: HTTP-based C2, Base64-encoded and XOR-protected communications, file upload from victims, network adapter enumeration, and Kaspersky AV presence checks.

Share:
For your environment

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.

THREAT ACTORS

Groups observed using it

1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
IndigoZebra

"...a previously undocumented piece of malware called xCaon."

via the hacker newsthehackernews.com
MITRE ATT&CK

Techniques & procedures

13 distinct techniques documented for this family, organized by ATT&CK tactic.

Execution

2 techniques
T1059.003Windows Command ShellEvidence3
TacticExecution

During the 2016 Ukraine Electric Power Attack, Sandworm Team used the xp_cmdshell command in MS-SQL. During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run cmd.exe commands on multiple victim machines. Numerous malware families and groups are described as using cmd.exe, cmd /c, Windows command shell, or command-line interfaces to execute commands, payloads, reconnaissance, persistence, cleanup, and ransomware actions.

T1106Native APIEvidence1
TacticExecution

Persistence

1 technique
T1547Boot or Logon Autostart ExecutionEvidence1
T1547Boot or Logon Autostart ExecutionEvidence1

Stealth

1 technique
T1140Deobfuscate/Decode Files or InformationEvidence4
TacticStealth

The content repeatedly describes malware and threat actors decoding, decrypting, or deobfuscating payloads, strings, configuration data, commands, and C2 traffic prior to execution or use, e.g., 'APT28 macro uses the command certutil -decode to decode contents of a .txt file storing the base64 encoded payload' and 'Action RAT can use Base64 to decode actor-controlled C2 server communications.'

Discovery

2 techniques
T1016System Network Configuration DiscoveryEvidence3
TacticDiscovery

The content repeatedly describes actors and malware using commands and APIs such as ipconfig /all, ifconfig, arp -a, route print, netsh interface show, GetAdaptersInfo, and GetIpNetTable to gather IP addresses, MAC addresses, DNS, DHCP, gateways, routing tables, ARP cache, proxy settings, and network adapter/interface details.

T1518.001Security Software DiscoveryEvidence1
TacticDiscovery

Collection

1 technique
T1005Data from Local SystemEvidence1
T1071.001Web ProtocolsEvidence3

The content repeatedly describes threat actors, malware, and campaigns using HTTP and/or HTTPS for command and control, including examples such as BlackEnergy communicating with C2 over HTTP POST requests and many other families using HTTP/S for C2.

T1105Ingress Tool TransferEvidence1
T1132Data EncodingEvidence2

C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding... APT19 HTTP malware variant used Base64 to encode communications to the C2 server... APT33 has used base64 to encode command and control traffic.

T1132.001Standard EncodingEvidence1
T1573.001Symmetric CryptographyEvidence1

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence2

Many entries state malware or actors can upload, transfer, send, or exfiltrate files from compromised hosts to command-and-control servers or attacker infrastructure.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution1

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping13

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.