← ClaudeAtlas

detect-data-exfiltrationlisted

Detection and response for data exfiltration over DNS and HTTPS/web channels, and for egress volume anomalies (MITRE ATT&CK T1041, T1048, T1048.003, T1071.004, T1567). Built from the October 2026 compromised-LiteLLM incident, where a stealer POSTed credentials to a lookalike domain. Ships the sigma-pack proxy rule for the known lookalike-domain exfil plus baselined hunts for DNS tunnelling and download/upload-ratio anomalies, keyed off web proxy logs, DNS telemetry (Sysmon Event ID 22, Windows DNS Server Event ID 256, Zeek dns.log), and firewall or NetFlow byte counts, with tuning, false-positive notes, and D3FEND countermeasures. Use when investigating an unexpected outbound connection or credential-stealer beacon, writing DNS or HTTPS exfiltration detections, hunting for data sent to a lookalike domain or over odd protocols, triaging an egress volume spike, or hardening egress after an AI-gateway or supply-chain compromise.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
Install: claude install-skill umbrasec-labs/umbra-blue
# Data Exfiltration - Detection and Response Exfiltration is the stage where stolen data actually leaves the estate, and attackers reach for the channels you already allow outbound: HTTPS to the open web and DNS to a resolver. Both are open almost everywhere, both carry encrypted or encoded payloads happily, and both blend into enormous volumes of legitimate traffic. This skill is defensive: it explains the technique only as far as detection and mitigation require, ships no stealer, tunnelling, or staging tooling, and treats the attacker's transport only as something to catch in your logs. ## TL;DR for defenders Turn on three egress log sources and keep them: **web/proxy access logs**, **DNS query logs**, and **firewall or NetFlow byte counts**. Then watch for three things. First, POSTs to a **known lookalike or never-before-seen domain** - the high-precision case, and the one the Sigma rule below pins to a named indicator. Second, **DNS queries with abnormal cardinality or label length** under a single parent domain, the tunnelling signal. Third, a **host whose outbound byte volume or upload-to-download ratio jumps above its own baseline**. The domain rule is a near-binary alarm; the DNS and volume analytics are hunts you baseline before you page on them. None is a silver bullet alone, so layer all three. ## Why it still matters in 2026 On October 21, 2026 a compromised **LiteLLM 1.107.0** release shipped a credential stealer that collected cloud, AI-provider, browser,