Conducting Malware Incident Response
When to Use
- EDR or antivirus detects malware execution on one or more endpoints
- A user reports suspicious system behavior indicative of malware infection
- Threat intelligence indicates a malware campaign targeting the organization's industry
- Network monitoring detects beaconing traffic consistent with known malware C2 patterns
- A file detonation in a sandbox returns a malicious verdict
Do not use for analyzing malware samples in a research context; use dedicated malware analysis procedures for reverse engineering.
Prerequisites
- EDR platform with process tree visibility and host isolation capability
- Malware sandbox environment (Cuckoo, ANY.RUN, Joe Sandbox, Hybrid Analysis)
- Access to threat intelligence platforms for malware family identification (VirusTotal, MalwareBazaar)
- Forensic imaging tools for evidence preservation (FTK Imager, KAPE)
- Clean system images or gold images for endpoint rebuild
- MITRE ATT&CK framework reference for technique mapping
Workflow
Step 1: Detect and Confirm Malware Presence
Validate the malware alert and gather initial indicators:
- Review EDR alert details: detection name, file path, hash (SHA-256), process tree
- Check if the detection is a known malware family or generic heuristic detection
- Query the file hash against VirusTotal, MalwareBazaar, and internal threat intelligence
- Examine the process execution chain to determine how the malware was delivered
Detection Summary:
File: C:\Users\jsmith\AppData\Local\Temp\update.exe
SHA-256: a1b2c3d4e5f6...
Detection: CrowdStrike: Malware/Qakbot | VirusTotal: 58/72 engines
Parent: WINWORD.EXE → cmd.exe → powershell.exe → update.exe
Delivery: Email attachment (Invoice-Nov2025.docm)
Network: HTTPS POST to 185.220.101[.]42:443 every 60s
Persistence: Scheduled Task "WindowsUpdate" → update.exe
Step 2: Scope the Infection
Determine how many systems are affected and the malware's propagation method:
- Use EDR to search for the malware hash, filename, and behavioral indicators across all endpoints
- Check for network-based spreading (SMB, WMI, PsExec, exploitation)
- Query email gateway logs for all recipients of the delivery email
- Search for C2 communications to the identified infrastructure from other internal hosts
- Check for persistence mechanisms on all identified infected hosts
Step 3: Contain Infected Systems
Execute containment per the active breach containment procedures:
- Network-isolate infected endpoints via EDR containment
- Block malware C2 infrastructure at firewall and DNS
- Block the malware hash in EDR prevention policy organization-wide
- Quarantine the delivery email from all mailboxes (if email-delivered)
- Disable compromised user accounts if credential theft is suspected
Step 4: Analyze the Malware
Perform sufficient analysis to support complete eradication:
- Submit the sample to a sandbox for dynamic analysis (behavioral report, dropped files, network IOCs)
- Identify all persistence mechanisms: registry keys, scheduled tasks, services, WMI subscriptions, startup folders
- Document all file system artifacts: dropped files, modified files, created directories
- Extract network IOCs: C2 domains, IPs, URLs, user agents, JA3/JA3S hashes
- Map observed behaviors to MITRE ATT&CK techniques
Malware Analysis Summary - Qakbot Variant
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Initial Access: T1566.001 - Spearphishing Attachment (.docm)
Execution: T1059.001 - PowerShell (encoded downloader)
Persistence: T1053.005 - Scheduled Task
Defense Evasion: T1055.012 - Process Hollowing (explorer.exe)
C2: T1071.001 - HTTPS with custom headers
Collection: T1005 - Data from Local System (browser credentials)
Exfiltration: T1041 - Exfiltration Over C2 Channel
Artifacts:
- C:\Users\*\AppData\Local\Temp\update.exe (dropper)
- C:\ProgramData\Microsoft\{GUID}\config.dll (payload)
- HKCU\Software\Microsoft\Windows\CurrentVersion\Run\{random} (backup persistence)
- Scheduled Task: "WindowsUpdate" (primary persistence)
Step 5: Eradicate the Malware
Remove all malware artifacts from every infected system:
- Terminate malicious processes and injected threads
- Delete malware files from all identified paths
- Remove persistence mechanisms (scheduled tasks, registry keys, services, WMI subscriptions)
- Clear browser credential stores if credential harvesting was confirmed
- Run a full EDR scan to verify no artifacts remain
- If eradication confidence is low, reimage the system from a known-clean gold image
Step 6: Recover and Validate
Restore systems to production and verify clean status:
- Reconnect contained systems to the network in stages
- Monitor for 72 hours for any recurrence of malware indicators
- Force password resets for all users on infected endpoints
- Verify that C2 traffic has completely ceased across the environment
- Update detection rules based on newly discovered IOCs from the investigation
- Distribute IOCs to threat intelligence sharing partners (ISAC, MISP)
Key Concepts
| Term |
Definition |
| Malware Family |
Classification of malware variants sharing code, infrastructure, or behavior patterns (e.g., Qakbot, Emotet, Cobalt Strike) |
| Process Hollowing |
Technique where malware creates a legitimate process in a suspended state, replaces its memory with malicious code, then resumes execution |
| Beacon |
Periodic network communication from malware to its C2 server, typically with a set interval and jitter for detection evasion |
| Dropper |
Initial malware component that downloads or unpacks the primary payload; often delivered via phishing |
| Persistence Mechanism |
Method used by malware to survive system reboots (registry run keys, scheduled tasks, services, WMI event subscriptions) |
| IOC (Indicator of Compromise) |
Observable artifact such as file hash, IP address, domain, or registry key that indicates malware presence |
Tools & Systems
- CrowdStrike Falcon / Microsoft Defender for Endpoint: EDR platforms for detection, containment, and threat hunting
- ANY.RUN / Joe Sandbox: Interactive malware sandboxes for dynamic behavioral analysis
- VirusTotal / MalwareBazaar: Malware intelligence platforms for sample identification and IOC enrichment
- KAPE (Kroll Artifact Parser and Extractor): Forensic triage tool for rapid artifact collection from infected endpoints
- YARA: Pattern-matching engine for creating custom malware detection rules based on observed indicators
Common Scenarios
Scenario: Emotet Loader Leading to Cobalt Strike Deployment
Context: EDR detects a macro-enabled document that spawns PowerShell, downloads an Emotet DLL, which subsequently loads a Cobalt Strike beacon. Three hosts are infected within 45 minutes.
Approach:
- Immediately isolate all three hosts and block C2 IPs at the perimeter
- Search email gateway for all recipients of the original phishing email and quarantine it
- Sweep all endpoints for the Emotet DLL hash and Cobalt Strike beacon indicators
- Analyze the Cobalt Strike beacon configuration to extract watermark, C2 profile, and staging URLs
- Check for credential harvesting (Mimikatz/LSASS dump) and lateral movement artifacts
- Eradicate all malware artifacts and reset credentials for affected users
Pitfalls:
- Focusing only on Emotet and missing the Cobalt Strike second-stage payload
- Failing to extract and block the Cobalt Strike Malleable C2 profile indicators
- Not checking for additional persistence beyond the initial detection (Emotet often installs multiple backup persistence mechanisms)
Output Format
MALWARE INCIDENT RESPONSE REPORT
=================================
Incident: INC-2025-1547
Malware Family: Qakbot (variant: Obama265)
Delivery Vector: Spearphishing attachment (Invoice-Nov2025.docm)
First Detection: 2025-11-15T14:23:17Z
Scope: 4 endpoints confirmed infected
INFECTION TIMELINE
14:18 UTC - Phishing email received by jsmith@corp.example.com
14:19 UTC - Macro executed in WINWORD.EXE
14:20 UTC - PowerShell downloads update.exe from staging server
14:21 UTC - update.exe establishes persistence (Scheduled Task)
14:23 UTC - C2 beacon initiated to 185.220.101[.]42
14:35 UTC - Lateral spread to WKSTN-087 via stolen credentials
14:42 UTC - EDR detection fires, SOC alerted
IOCs EXTRACTED
File Hashes: [SHA-256 list]
C2 Domains: [domain list]
C2 IPs: [IP list]
File Paths: [artifact paths]
ERADICATION STATUS
[x] All malware artifacts removed from 4 hosts
[x] Persistence mechanisms deleted
[x] C2 infrastructure blocked
[x] Compromised credentials reset
[x] Email quarantined from all mailboxes
RECOMMENDATIONS
1. Deploy YARA rule for Qakbot variant detection
2. Block macro execution in documents from external senders
3. Implement application whitelisting on finance workstations
1---2name: conducting-malware-incident-response-23description: Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including trojan/worm/ransomware outbreaks, malware triage, or infected endpoint remediation.4domain: cybersecurity5subdomain: incident-response6tags:7- malware-response8- malware-analysis9- eradication10- endpoint-remediation11- MITRE-ATT&CK12mitre_attack:13- T120414- T102715- T105516- T105917- T148618version: 1.0.019author: mahipal20license: Apache-2.021d3fend_techniques:22- File Metadata Consistency Validation23- Application Protocol Command Analysis24- Identifier Analysis25- Content Format Conversion26- Message Analysis27nist_csf:28- RS.MA-0129- RS.MA-0230- RS.AN-0331- RC.RP-0132metadata:33 source: https://skillmd.com/skills/26zl/conducting-malware-incident-response-234---3536# Conducting Malware Incident Response3738## When to Use3940- EDR or antivirus detects malware execution on one or more endpoints41- A user reports suspicious system behavior indicative of malware infection42- Threat intelligence indicates a malware campaign targeting the organization's industry43- Network monitoring detects beaconing traffic consistent with known malware C2 patterns44- A file detonation in a sandbox returns a malicious verdict4546**Do not use** for analyzing malware samples in a research context; use dedicated malware analysis procedures for reverse engineering.4748## Prerequisites4950- EDR platform with process tree visibility and host isolation capability51- Malware sandbox environment (Cuckoo, ANY.RUN, Joe Sandbox, Hybrid Analysis)52- Access to threat intelligence platforms for malware family identification (VirusTotal, MalwareBazaar)53- Forensic imaging tools for evidence preservation (FTK Imager, KAPE)54- Clean system images or gold images for endpoint rebuild55- MITRE ATT&CK framework reference for technique mapping5657## Workflow5859### Step 1: Detect and Confirm Malware Presence6061Validate the malware alert and gather initial indicators:6263- Review EDR alert details: detection name, file path, hash (SHA-256), process tree64- Check if the detection is a known malware family or generic heuristic detection65- Query the file hash against VirusTotal, MalwareBazaar, and internal threat intelligence66- Examine the process execution chain to determine how the malware was delivered6768```69Detection Summary:70File: C:\Users\jsmith\AppData\Local\Temp\update.exe71SHA-256: a1b2c3d4e5f6...72Detection: CrowdStrike: Malware/Qakbot | VirusTotal: 58/72 engines73Parent: WINWORD.EXE → cmd.exe → powershell.exe → update.exe74Delivery: Email attachment (Invoice-Nov2025.docm)75Network: HTTPS POST to 185.220.101[.]42:443 every 60s76Persistence: Scheduled Task "WindowsUpdate" → update.exe77```7879### Step 2: Scope the Infection8081Determine how many systems are affected and the malware's propagation method:8283- Use EDR to search for the malware hash, filename, and behavioral indicators across all endpoints84- Check for network-based spreading (SMB, WMI, PsExec, exploitation)85- Query email gateway logs for all recipients of the delivery email86- Search for C2 communications to the identified infrastructure from other internal hosts87- Check for persistence mechanisms on all identified infected hosts8889### Step 3: Contain Infected Systems9091Execute containment per the active breach containment procedures:9293- Network-isolate infected endpoints via EDR containment94- Block malware C2 infrastructure at firewall and DNS95- Block the malware hash in EDR prevention policy organization-wide96- Quarantine the delivery email from all mailboxes (if email-delivered)97- Disable compromised user accounts if credential theft is suspected9899### Step 4: Analyze the Malware100101Perform sufficient analysis to support complete eradication:102103- Submit the sample to a sandbox for dynamic analysis (behavioral report, dropped files, network IOCs)104- Identify all persistence mechanisms: registry keys, scheduled tasks, services, WMI subscriptions, startup folders105- Document all file system artifacts: dropped files, modified files, created directories106- Extract network IOCs: C2 domains, IPs, URLs, user agents, JA3/JA3S hashes107- Map observed behaviors to MITRE ATT&CK techniques108109```110Malware Analysis Summary - Qakbot Variant111━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━112Initial Access: T1566.001 - Spearphishing Attachment (.docm)113Execution: T1059.001 - PowerShell (encoded downloader)114Persistence: T1053.005 - Scheduled Task115Defense Evasion: T1055.012 - Process Hollowing (explorer.exe)116C2: T1071.001 - HTTPS with custom headers117Collection: T1005 - Data from Local System (browser credentials)118Exfiltration: T1041 - Exfiltration Over C2 Channel119120Artifacts:121- C:\Users\*\AppData\Local\Temp\update.exe (dropper)122- C:\ProgramData\Microsoft\{GUID}\config.dll (payload)123- HKCU\Software\Microsoft\Windows\CurrentVersion\Run\{random} (backup persistence)124- Scheduled Task: "WindowsUpdate" (primary persistence)125```126127### Step 5: Eradicate the Malware128129Remove all malware artifacts from every infected system:130131- Terminate malicious processes and injected threads132- Delete malware files from all identified paths133- Remove persistence mechanisms (scheduled tasks, registry keys, services, WMI subscriptions)134- Clear browser credential stores if credential harvesting was confirmed135- Run a full EDR scan to verify no artifacts remain136- If eradication confidence is low, reimage the system from a known-clean gold image137138### Step 6: Recover and Validate139140Restore systems to production and verify clean status:141142- Reconnect contained systems to the network in stages143- Monitor for 72 hours for any recurrence of malware indicators144- Force password resets for all users on infected endpoints145- Verify that C2 traffic has completely ceased across the environment146- Update detection rules based on newly discovered IOCs from the investigation147- Distribute IOCs to threat intelligence sharing partners (ISAC, MISP)148149## Key Concepts150151| Term | Definition |152|------|------------|153| **Malware Family** | Classification of malware variants sharing code, infrastructure, or behavior patterns (e.g., Qakbot, Emotet, Cobalt Strike) |154| **Process Hollowing** | Technique where malware creates a legitimate process in a suspended state, replaces its memory with malicious code, then resumes execution |155| **Beacon** | Periodic network communication from malware to its C2 server, typically with a set interval and jitter for detection evasion |156| **Dropper** | Initial malware component that downloads or unpacks the primary payload; often delivered via phishing |157| **Persistence Mechanism** | Method used by malware to survive system reboots (registry run keys, scheduled tasks, services, WMI event subscriptions) |158| **IOC (Indicator of Compromise)** | Observable artifact such as file hash, IP address, domain, or registry key that indicates malware presence |159160## Tools & Systems161162- **CrowdStrike Falcon / Microsoft Defender for Endpoint**: EDR platforms for detection, containment, and threat hunting163- **ANY.RUN / Joe Sandbox**: Interactive malware sandboxes for dynamic behavioral analysis164- **VirusTotal / MalwareBazaar**: Malware intelligence platforms for sample identification and IOC enrichment165- **KAPE (Kroll Artifact Parser and Extractor)**: Forensic triage tool for rapid artifact collection from infected endpoints166- **YARA**: Pattern-matching engine for creating custom malware detection rules based on observed indicators167168## Common Scenarios169170### Scenario: Emotet Loader Leading to Cobalt Strike Deployment171172**Context**: EDR detects a macro-enabled document that spawns PowerShell, downloads an Emotet DLL, which subsequently loads a Cobalt Strike beacon. Three hosts are infected within 45 minutes.173174**Approach**:1751. Immediately isolate all three hosts and block C2 IPs at the perimeter1762. Search email gateway for all recipients of the original phishing email and quarantine it1773. Sweep all endpoints for the Emotet DLL hash and Cobalt Strike beacon indicators1784. Analyze the Cobalt Strike beacon configuration to extract watermark, C2 profile, and staging URLs1795. Check for credential harvesting (Mimikatz/LSASS dump) and lateral movement artifacts1806. Eradicate all malware artifacts and reset credentials for affected users181182**Pitfalls**:183- Focusing only on Emotet and missing the Cobalt Strike second-stage payload184- Failing to extract and block the Cobalt Strike Malleable C2 profile indicators185- Not checking for additional persistence beyond the initial detection (Emotet often installs multiple backup persistence mechanisms)186187## Output Format188189```190MALWARE INCIDENT RESPONSE REPORT191=================================192Incident: INC-2025-1547193Malware Family: Qakbot (variant: Obama265)194Delivery Vector: Spearphishing attachment (Invoice-Nov2025.docm)195First Detection: 2025-11-15T14:23:17Z196Scope: 4 endpoints confirmed infected197198INFECTION TIMELINE19914:18 UTC - Phishing email received by jsmith@corp.example.com20014:19 UTC - Macro executed in WINWORD.EXE20114:20 UTC - PowerShell downloads update.exe from staging server20214:21 UTC - update.exe establishes persistence (Scheduled Task)20314:23 UTC - C2 beacon initiated to 185.220.101[.]4220414:35 UTC - Lateral spread to WKSTN-087 via stolen credentials20514:42 UTC - EDR detection fires, SOC alerted206207IOCs EXTRACTED208File Hashes: [SHA-256 list]209C2 Domains: [domain list]210C2 IPs: [IP list]211File Paths: [artifact paths]212213ERADICATION STATUS214[x] All malware artifacts removed from 4 hosts215[x] Persistence mechanisms deleted216[x] C2 infrastructure blocked217[x] Compromised credentials reset218[x] Email quarantined from all mailboxes219220RECOMMENDATIONS2211. Deploy YARA rule for Qakbot variant detection2222. Block macro execution in documents from external senders2233. Implement application whitelisting on finance workstations224```