Has used Pastebin to check the version of beaconing malware and redirect to another Pastebin hosting updated malware.1
- Tactic
- Command and Control
- Platforms
- ESXi, Linux, macOS, Windows
- Version
- 1.1
- Created
- 14 March 2020
- Last modified
- 12 May 2026
Adversaries may use an existing, legitimate external Web service to host information that points to additional command and control (C2) infrastructure. Adversaries may post content, known as a dead drop resolver, on Web services with embedded (and often obfuscated/encoded) domains or IP addresses. Once infected, victims will reach out to and be redirected by these resolvers.
Dead Drop Resolver MITRE reference T1102.001
6 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.
Used legitimate websites for C2 through dead drop resolvers (DDR), including GitHub, Pastebin, and Microsoft TechNet.1
Has used TRANSLATEXT and a dead drop resolver to retrieve configurations and commands from a public blog site.1
BRONZE BUTLER's MSGET downloader uses a dead drop resolver to access malicious payloads.1
Has used an RSS feed on Livejournal to update a list of encrypted C2 server names.1
Hides base64-encoded and encrypted C2 server locations in comments on legitimate websites.1
All 6 groups for this technique
2 campaigns have been recorded using this technique. Listed newest first; dates are year-granularity and attribution is MITRE’s.
During the 3CX Supply Chain Attack, AppleJeus leveraged a GitHub repository to host icon files containing the command and control URL.12
During C0017, APT41 used dead drop resolvers on two separate tech community forums for their KEYPLUG Windows-version backdoor; notably APT41 updated the community forum posts frequently with new dead drop resolvers during the campaign.1
All 2 campaigns for this technique
19 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.
Has leveraged GitHub commit-search API to recover fallback C2 domains stored in auto-created public Github repositories.12345
Can periodically poll a decentralized Internet Computer Protocol (ICP) canister to retrieve a dynamic URL for payload delivery.123
Has obtained the C2 address from Ethereum blockchain nodes.12
Has leveraged blockchain-based C2 infrastructure to include Solana blockchain that contains additional C2 details within the memo field.123456 GlassWorm has also leveraged Google Calendar to host encoded data.356
Has the ability to retrieve a C2 address from a dead drop URL.1
Has used a dead drop resolver to retrieve configurations and commands from a public blog site.1
All 19 software entries for this technique · 6 newest in this preview
Offense vs defense T1102.001
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
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.
Dead Drop Resolver detection strategy DET0058
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.
Detection Strategy for Web Service: Dead Drop Resolver
AN0158 · Windows
Detection of a process or script that accesses a common web service to retrieve content containing obfuscated indicators of a secondary C2 server (dead drop resolver behavior).
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 | etw:Microsoft-Windows-NDIS-PacketCapture | TLS Handshake/Network Flow |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TargetDomain | FQDN or IP for the hosting site of the dead drop (e.g., pastebin.com, twitter.com) |
| TimeWindow | Defines how close in time the suspicious network and process behavior must occur |
| UserContext | Filter by user or system accounts to reduce noise |
AN0159 · Linux
Detection of a process or script that accesses a common web service to retrieve content containing obfuscated indicators of a secondary C2 server (dead drop resolver behavior).
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 | auditd:SYSCALL | connect |
| Network Traffic ContentDC0085 | NSM:Flow | HTTP/TLS Logs |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TargetDomain | Dead drop hosting domain (e.g., GitHub, Google Docs) |
| PayloadEntropyThreshold | Detects high entropy in payloads signaling obfuscation |
| TimeWindow | Causal proximity between access to resolver and follow-up connections |
AN0160 · macOS
Detection of a process or script that accesses a common web service to retrieve content containing obfuscated indicators of a secondary C2 server (dead drop resolver behavior).
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 | macos:osquery | process_events/socket_events |
| Network Traffic ContentDC0085 | macos:unifiedlog | subsystem: com.apple.network |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| TargetService | Known services abused for D2 (e.g., iCloud, Dropbox) |
| UserContext | Useful to isolate rare users accessing web services for C2 |
| TimeWindow | Max time gap between dead drop resolver fetch and follow-on traffic |
AN0161 · ESXi
Detection of a process or script that accesses a common web service to retrieve content containing obfuscated indicators of a secondary C2 server (dead drop resolver behavior).
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 Traffic FlowDC0078 | esxi:vobd | Network Events |
| Network Connection CreationDC0082 | NSM:Firewall | Outbound Connections |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| DestinationIP | Identifies unusual IP destinations embedded in traffic |
| Protocol | Used to detect uncommon protocols (e.g., DNS over HTTPS) |
| TimeWindow | Used to correlate outbound web requests with process execution |
Network intrusion detection and prevention systems that use network signatures to identify traffic for specific adversary malware can be used to mitigate activity at the network level.
Web proxies can be used to enforce external network communication policy that prevents use of unauthorized external services.