Detection rules › Splunk

3CX Supply Chain Attack Network Indicators

Author
Michael Haag, Splunk
Source
upstream

The following analytic identifies DNS queries to domains associated with the 3CX supply chain attack. It leverages the Network_Resolution datamodel to detect these suspicious domain indicators. This activity is significant because it can indicate a potential compromise stemming from the 3CX supply chain attack, which is known for distributing malicious software through trusted updates. If confirmed malicious, this activity could allow attackers to establish a foothold in the network, exfiltrate sensitive data, or further propagate malware, leading to extensive damage and data breaches.

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1195.002 Supply Chain Compromise: Compromise Software Supply Chain

Event coverage

ProviderEvent IDTitle
Sysmon22DNSEvent (DNS query)

Stages and Predicates

Stage 1: tstats

tstats WHERE NOT DNS.query IN ("-", "unknown") DNS.query="*" BY DNS.answer, DNS.answer_count, DNS.query, DNS.query_count, DNS.reply_code_id, DNS.src, DNS.vendor_product

Stage 2: search

search

Stage 3: search

search

Stage 4: search

search

Stage 5: lookup

lookup <lookup> Description, domain, isIOC, query

Stage 6: search

search isIOC=true

Stage 7: search

search `macro`

Exclusions

Top-level NOT(...) conjuncts — predicates this rule actively suppresses.

StageFieldKindExcluded values
1dns.question.namein"-", "unknown"

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
DNS.queryeq
  • * corpus 3 (splunk 3)
isIOCeq
  • true