← Sigma detections
Sigma · CVE exploitation
CVE-2026-35273 exploitation domain indicators
- severity
- high
- confidence
- 95/100
- generated
- 19 Nov 2026
- Linked CVE
- CVE-2026-35273
1 domain indicator threat feeds tag with CVE-2026-35273, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).
False-positive notes
1 indicator. Evidence: 1 listed by 2 or more independent non-scanner feed publishers. Listed by 3 independent sources in all. Newest feed sighting 2026-11-19, oldest 2026-11-19 (a live actor sweep accepts at most 90 days). Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists; sinkhole NS / DNS verified for 1 of 1 domain indicator. Re-validate against last_seen before blocking: infrastructure is re-assigned.
References
title: Skopnix - CVE-2026-35273 exploitation domain indicatorsid: 06f5b702-af84-58f4-8d11-612de26be928status: experimentaldescription: 1 domain indicator threat feeds tag with CVE-2026-35273, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).references: - https://skopnix.com/cve/CVE-2026-35273author: skopnixdate: '2026-11-19'tags: - attack.command-and-control - attack.t1071logsource: category: dnsdetection: selection: query: - azurenetfiles.net condition: selectionfalsepositives: - Legitimate services sharing the address; verify against skopnix confidence + last_seenlevel: highskopnix-sigma-cve-cve-2026-35273-domain-b8f1b3fe.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.