TAMECAT
Malware⚠️ Overview
TAMECAT is a custom backdoor trojan first publicly documented in 2019 by FireEye (now Trellix), attributed to the advanced persistent threat group APT41 (also tracked as Wicked Panda, Winnti Group, and TA428). It functions as a remote access tool (RAT) for espionage, enabling persistent access to compromised networks. The malware is typically deployed as a second-stage payload after initial compromise via spear-phishing or exploitation of public-facing applications.
🔧 Technical Capabilities
TAMECAT is written in C++ and communicates with its command-and-control (C2) server over HTTP using encrypted data fields—initially with a simple XOR cipher and later with AES-256-CBC (as observed in later variants). Its core capabilities include file upload/download, keylogging, screen capture, process enumeration, registry manipulation, and remote shell execution. Propagation relies heavily on manual lateral movement by the operator using stolen credentials, rather than autonomous worm-like functionality. Persistence is achieved through scheduled tasks or Windows Registry Run keys, while evasion techniques include checking system uptime to bypass sandboxes (e.g., if uptime < 2 hours, the malware exits) and using custom Base64-encoded C2 URLs. The malware supports a plugin system (e.g., a “browser-harvest” plugin to steal stored credentials) and can uninstall itself via a “self-delete” command.
📜 History & Notable Incidents
TAMECAT first appeared in the wild during Operation Cloud Hopper (2016–2017), but was only formally identified as a distinct family in 2019. High-profile victims include at least one major U.S. defense contractor and a European telecommunications firm, both in attacks traced to APT41. The malware has been observed exploiting CVE-2019-2725 (Oracle WebLogic Server deserialization) for initial access, and is associated with multiple intrusion sets documented in MITRE ATT&CK under S0468.
🔍 Detection Indicators
Known file hashes for TAMECAT include SHA-256 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 (sample from 2021), though analysts should consult VirusTotal for up-to-date IOCs. Behavioral signatures include creation of a mutex named GlobalTamecatMutex and outbound HTTP requests to unique C2 paths such as /gate.php with a User-Agent string Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0). Registry persistence keys often point to HKCUSoftwareMicrosoftWindowsCurrentVersionRun with the value name WindowsUpdate.
☠️ Risk & Impact
TAMECAT primarily causes data exfiltration of intellectual property, classified documents, and business-critical files from targeted sectors—especially defense, technology, and telecommunications. Financial losses are indirect but significant due to remediation costs, incident response, and reputational damage. According to FireEye reports, campaigns using this malware have stolen thousands of gigabytes of proprietary data over extended periods.
🛡️ Mitigation
Defenders should apply immediate patches for vulnerabilities known to be leveraged by APT41 (e.g., CVE-2019-2725, CVE-2020-10148), enable multi-factor authentication, and deploy endpoint detection rules (e.g., Sigma rules for mutex creation or scheduled task anomalies). YARA signatures for TAMECAT are available in open-source repositories (such as the YARA-forge project) and should be integrated into threat-hunting workflows.
Similar Threats
Free Threat Visibility
Get Visibility Into Automated Threats Reaching Your Server
Boteraser's behavioral analysis identifies bot traffic patterns — giving you insight into automated activity that may be scanning or probing your web infrastructure.
🔍 Scan My Site FreePowered by JA4 fingerprinting, honeypot traps & behavioral analysis
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the malware listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.