ATT&CK coverage › Technique

Adversary-in-the-Middle: DHCP Spoofing T1557.003

Adversaries may redirect network traffic to adversary-owned systems by spoofing Dynamic Host Configuration Protocol (DHCP) traffic and acting as a malicious DHCP server on the victim network. By achieving the adversary-in-the-middle (AiTM) position, adversaries may collect network communications, including passed credentials, especially those sent over insecure, unencrypted protocols. This may also enable follow-on behaviors such as Network Sniffing or Transmitted Data Manipulation.

Events covered

3 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Security-Auditing4662An operation was performed on an object.
Security-Auditing5136A directory service object was modified.
Security-Auditing5137A directory service object was created.

Authoring guide

Patterns shared across the 1 rule above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (3 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
AdditionalInfo1match 1CN=MicrosoftDNS, BAAAA, UWhRCA
ObjectClass1eq 1dnsNode
ObjectDN1match 1CN=MicrosoftDNS, BAAAA, UWhRCA

Top indicator values (7 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
ObjectDNmatchBAAAA1
AdditionalInfomatchUWhRCA1
AdditionalInfomatchCN=MicrosoftDNS1
ObjectDNmatchUWhRCA1
ObjectClasseqdnsNode13
AdditionalInfomatchBAAAA1
ObjectDNmatchCN=MicrosoftDNS1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 1 rule