Mustang PandaG0129 ↗
Has utilized TLS record headers in network packets to impersonate various versions of TLS protocols to blend in with legitimate network traffic. Mustang Panda has used FakeTLS to communicate with its C2 servers.1
tfMITRE ATT&CK sub-technique
Protocol or Service Impersonation T1001.003
sub-technique of T1001 Data Obfuscation
- Tactic
- Command and Control
- Platforms
- ESXi, Linux, macOS, Windows
- Version
- 2.1
- Created
- 15 March 2020
- Last modified
- 12 May 2026
- Contributor
- James Emery-Callcott, Emerging Threats Team, Proofpoint
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts. By impersonating legitimate protocols or web services, adversaries can make their command and control traffic blend in with legitimate network traffic.
ReconResource DevInitial AccessExecutionPersistencePriv EscStealthDef ImpairmentCred AccessDiscoveryLateral MoveCollectionC2ExfiltrationImpact
3
Threat groups64th pct
Threat groups64th percentile · 64% of ATT&CK techniques have this many threat groups attributed or fewer.1
Campaigns72nd pct
Campaigns72nd percentile · 72% of ATT&CK techniques have this many campaigns recorded or fewer.18
Tools & malwareTop 19%
Tools & malware81st percentile · 81% of ATT&CK techniques have this many tools implementing them or fewer.3
Detection rules54th pct
Detection rules54th percentile · 54% of ATT&CK techniques have this many detection rules written or fewer.Protocol or Service Impersonation MITRE reference T1001.003
64th pctamong all ATT&CK techniques for number of groups
3 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
HigaisaG0126 ↗
Used a FakeTLS session for C2 communications.1
Lazarus GroupG0032 ↗
Malware also uses a unique form of communication encryption known as FakeTLS that mimics TLS but uses a different encryption method, potentially evading SSL traffic inspection/decryption.1234
All 3 groups for this technique
1 campaign has been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
C0017C0017 ↗
During C0017, APT41 frequently configured the URL endpoints of their stealthy passive backdoor LOWKEY.PASSIVE to masquerade as normal web application traffic on an infected server.1
All 1 campaigns for this technique
18 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
TONESHELLS1239 ↗
Used FakeTLS headers in network packets to impersonate various versions of TLS protocols to blend in with legitimate network traffic.12 TONESHELL variants have utilized FakeTLS headers with the bytes 0x17 0x03 0x03 to represent TLSv1.2 and 0x17 0x03 0x04 for TLSv1.3.2
PUBLOADS1228 ↗
Has modified HTTP POST requests to resemble legitimate communications.12 PUBLOAD used FakeTLS headers in network packets to impersonate various versions of TLS protocols to blend in with legitimate network traffic. PUBLOAD has utilized FakeTLS headers with the bytes 17 03 03.3
StarProxyS1227 ↗
Has utilized TLS record headers in network packets to impersonate various versions of TLS protocols to blend in with legitimate network traffic. StarProxy used FakeTLS to communicate with its C2 server.1
BOOKWORMS1226 ↗
Has modified HTTP POST requests to resemble legitimate communications.1
FRAMESTINGS1120 ↗
Uses a cookie named DSID to mimic the name of a cookie used by Ivanti Connect Secure appliances for maintaining VPN sessions.1
NinjaS1100 ↗
Has the ability to mimic legitimate services with customized HTTP URL paths and headers to hide malicious traffic.1
All 18 software entries for this technique · 6 newest in this preview
Offense vs defense T1001.003
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Range
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Campaigns · 1Sigma rules (cumulative) · 3Splunk ESCU (cumulative) · 0
first rule: 2019 Q1 · 1 of 1 campaigns plottedProtocol or Service Impersonation detection strategy DET0470
MITRE names one behaviour worth catching for this technique and breaks it into 4 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detecting Protocol or Service Impersonation via Anomalous TLS, HTTP Header, and Port Mismatch Correlation
4 platforms
AN1294 · Windows
Untrusted processes creating outbound TLS/HTTPS connections with malformed certificates or header fields, often mismatched with target service behavior. Detects protocol impersonation attempts via traffic metadata analysis and host process lineage.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Connection CreationDC0082 | WinEventLog:Sysmon | EventCode=3, 22 |
| Network Traffic ContentDC0085 | NSM:Flow | SSL/TLS Handshake Analysis |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| IssuerOrgFilter | Organizations in certificate issuer fields to allowlist or monitor. |
| UserContext | Restrict detection to non-system users or external-facing applications. |
| HeaderSignatureMatch | Specific HTTP header anomalies or patterns (e.g., missing User-Agent). |
AN1295 · Linux
Detection of binaries spawning encrypted sessions using OpenSSL or curl to external services with mismatched ports/protocols. Identifies behavior where internal services simulate trusted cloud service traffic patterns.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process CreationDC0032 | auditd:SYSCALL | execve |
| Network Traffic ContentDC0085 | NSM:Flow | Network Capture TLS/HTTP |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ProtocolMatchConfidence | Threshold for header-field mismatch against expected service behavior. |
| TimeWindow | Correlation window between process spawn and encrypted session. |
AN1296 · macOS
Unsigned or suspicious applications initiating network traffic claiming to be browser, mail, or cloud clients. Detects impersonation via TLS fingerprint and User-Agent string deviation.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Process MetadataDC0034 | macos:osquery | Process Execution + Hash |
| Network Connection CreationDC0082 | macos:unifiedlog | Outbound Traffic |
| Network Traffic ContentDC0085 | NSM:Content | HTTP Header Metadata |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ParentProcessFilter | Limit detections to children of suspicious binaries. |
| HeaderAnomalyScore | Threshold for deviation from expected headers (User-Agent, Host). |
AN1297 · ESXi
ESXi hosts initiating connections from non-standard daemons mimicking HTTP/HTTPS or SNMP traffic, but with irregular payload formats or expired/unsigned TLS certificates.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Network Connection CreationDC0082 | esxi:hostd | Service-Based Network Connection |
| Network Traffic ContentDC0085 | NSM:Content | TLS Fingerprint and Certificate Analysis |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TLSFingerprintMatch | Allows matching against known-good or known-bad JA3/JA3S hashes. |
| AllowedServicePorts | Tune for expected network ports per ESXi role. |
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate some obfuscation activity at the network level.