Detecting Fileless Malware Techniques
Overview
Cybersecurity skill for detecting fileless malware techniques. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"detecting fileless malware techniques"
"Detects and analyzes fileless malware that operates entirely in memory using Pow"
EDR alerts indicate suspicious behavior from trusted system binaries (PowerShell, mshta, wmic, regsvr32)
Investigating attacks that leave no traditional malware files on disk
Analyzing WMI event subscriptions, registry-stored payloads, or scheduled task abuse for persistence
Building detection rules for LOLBin (Living Off the Land Binary) abuse in enterprise environments
Memory forensics reveals malicious code but no corresponding files exist on the filesystem
Do not use for traditional file-based malware; standard static and dynamic analysis methods are more appropriate for disk-resident malware.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Sysmon installed and configured with comprehensive logging (process creation, WMI events, registry changes)
- PowerShell Script Block Logging and Module Logging enabled
- Volatility 3 for memory forensics of fileless malware artifacts
- Process Monitor (ProcMon) for real-time system activity monitoring
- Windows Event Log access with adequate retention policies
- Autoruns for identifying persistence mechanisms
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Define Detection Scope — Identify the specific fileless malware techniques techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.
- Collect Baseline Data — Gather historical logs and establish normal behavior patterns for fileless malware techniques.
- Build Detection Queries — Write detection rules, Sigma rules, or SIEM queries targeting fileless malware techniques indicators.
- Execute Hunts — Run queries against the collected data, starting with broad filters and narrowing down.
- Triage Results — Investigate alerts, filter false positives, and validate findings against known-good behavior.
- Document Findings — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.
Tools
- SIEM Platform — Central log aggregation and query execution
- Sigma Rules — Vendor-agnostic detection rule format
- MITRE ATT&CK Navigator — Technique mapping and coverage analysis
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: detecting-fileless-malware-techniques3description: Use when detects and analyzes fileless malware that operates entirely4 in memory using PowerShell, WMI, .NET reflection, registry-resident payloads, and5 living-off-the-land binaries (LOLBins) without writing traditional executable files6 to disk. Activates for requests involving fileless threat detection, in-memory malware7 investigation, LOLBin abuse analysis, or WMI persistence examination. . Use when8 working with detecting fileless malware techniques.9domain: cybersecurity10tags:11- malware12- fileless13- LOLBins14- memory-analysis15- detection16subdomain: malware-analysis17version: 1.0.018author: oyi7719license: Apache-2.020d3fend_techniques:21- Executable Denylisting22- Execution Isolation23- File Metadata Consistency Validation24- Content Format Conversion25- File Content Analysis26nist_csf:27- DE.AE-0228- RS.AN-0329- ID.RA-0130- DE.CM-0131category: cybersecurity32metadata:33 source: https://skillmd.com/skills/oyi77/detecting-fileless-malware-techniques34---3536# Detecting Fileless Malware Techniques3738## Overview3940Cybersecurity skill for detecting fileless malware techniques. Follows industry best practices and security standards.4142## When to Use43**Trigger phrases:**44- "detecting fileless malware techniques"45- "Detects and analyzes fileless malware that operates entirely in memory using Pow"464748- EDR alerts indicate suspicious behavior from trusted system binaries (PowerShell, mshta, wmic, regsvr32)49- Investigating attacks that leave no traditional malware files on disk50- Analyzing WMI event subscriptions, registry-stored payloads, or scheduled task abuse for persistence51- Building detection rules for LOLBin (Living Off the Land Binary) abuse in enterprise environments52- Memory forensics reveals malicious code but no corresponding files exist on the filesystem5354**Do not use** for traditional file-based malware; standard static and dynamic analysis methods are more appropriate for disk-resident malware.555657## When NOT to Use5859- When you lack proper authorization for testing60- For production systems without change management61- When the task requires legal or compliance expertise beyond technical scope626364## Prerequisites6566- Sysmon installed and configured with comprehensive logging (process creation, WMI events, registry changes)67- PowerShell Script Block Logging and Module Logging enabled68- Volatility 3 for memory forensics of fileless malware artifacts69- Process Monitor (ProcMon) for real-time system activity monitoring70- Windows Event Log access with adequate retention policies71- Autoruns for identifying persistence mechanisms7273## Workflow7475```python76# Example: IOC detection77import re7879IOC_PATTERNS = {80 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",81 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",82 "hash_md5": r"\b[a-f0-9]{32}\b",83 "hash_sha256": r"\b[a-f0-9]{64}\b",84}8586def extract_iocs(text: str) -> dict:87 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}88```89901. **Define Detection Scope** — Identify the specific fileless malware techniques techniques or indicators to hunt. Map to MITRE ATT&CK tactics/techniques where applicable.912. **Collect Baseline Data** — Gather historical logs and establish normal behavior patterns for fileless malware techniques.923. **Build Detection Queries** — Write detection rules, Sigma rules, or SIEM queries targeting fileless malware techniques indicators.934. **Execute Hunts** — Run queries against the collected data, starting with broad filters and narrowing down.945. **Triage Results** — Investigate alerts, filter false positives, and validate findings against known-good behavior.956. **Document Findings** — Record confirmed detections, IOCs, and affected systems. Update detection rules based on findings.9697## Tools9899- **SIEM Platform** — Central log aggregation and query execution100- **Sigma Rules** — Vendor-agnostic detection rule format101- **MITRE ATT&CK Navigator** — Technique mapping and coverage analysis102103104## Process1051061. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1071. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1081. **Reporting** — Document IOCs, write findings, provide remediation recommendations109110## Verification111112- [ ] All fileless malware techniques procedures executed completely and documented113- [ ] Findings validated against multiple data sources114- [ ] False positives identified and filtered115- [ ] Results documented with evidence and timestamps116- [ ] Recommendations provided with risk-based prioritization117118## Anti-Rationalization Table119120| Rationalization | Reality |121|---|---|122| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |123| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |124| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |