Skip to content

Commit 3d9270d

Browse files
committed
Another snapattack windows batch
1 parent 8c42801 commit 3d9270d

5 files changed

Lines changed: 256 additions & 0 deletions
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
name: Windows Dir Piped to Findstr Activity
2+
id: 43cd7a59-3d52-4969-a01a-d677630b1426
3+
version: 1
4+
creation_date: '2026-07-30'
5+
modification_date: '2026-07-30'
6+
author: Raven Tait, Splunk
7+
status: production
8+
type: Anomaly
9+
description: The following analytic detects the execution of the `dir` command piped to `findstr` on Windows systems. This technique is commonly used by attackers during the reconnaissance phase to enumerate files, directories, or sensitive data by filtering directory listings for specific strings or patterns. While this command combination can have legitimate administrative uses, adversaries frequently leverage it to locate credentials, configuration files, or other high-value targets on a compromised system. If confirmed malicious, this activity could indicate an attacker is actively mapping the file system in preparation for data exfiltration, lateral movement, or further exploitation.
10+
data_source:
11+
- Sysmon EventID 1
12+
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process="*dir*|*findstr*" by Processes.process Processes.vendor_product Processes.user_id Processes.process_hash Processes.parent_process_name Processes.parent_process_exec Processes.action Processes.dest Processes.process_current_directory Processes.process_path Processes.process_integrity_level Processes.original_file_name Processes.parent_process Processes.parent_process_path Processes.parent_process_guid Processes.parent_process_id Processes.process_guid Processes.process_id Processes.user Processes.process_name | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`| `security_content_ctime(lastTime)`| `windows_dir_piped_to_findstr_activity_filter`'
13+
how_to_implement: The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint` data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.
14+
known_false_positives: Legitimate administrative tasks and scripts may use `dir` piped to `findstr` for routine file searches. Filter based on known user behavior and approved administrative activity.
15+
drilldown_searches:
16+
- earliest_offset: $info_min_time$
17+
latest_offset: $info_max_time$
18+
name: View the detection results for - "$user$" and "$dest$"
19+
search: '%original_detection_search% | search user = "$user$" dest = "$dest$"'
20+
- name: View risk events for the last 7 days for - "$user$" and "$dest$"
21+
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user$", "$dest$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
22+
earliest_offset: 7d
23+
latest_offset: '0'
24+
intermediate_findings:
25+
entities:
26+
- field: dest
27+
type: system
28+
score: 20
29+
message: Suspicious findstr Activity by $user$ on $dest$ via $process_name$.
30+
- field: user
31+
type: user
32+
score: 20
33+
message: Suspicious findstr Activity by $user$ on $dest$ via $process_name$.
34+
threat_objects:
35+
- field: parent_process_name
36+
type: parent_process_name
37+
- field: process_name
38+
type: process_name
39+
analytic_story:
40+
- Suspicious Command-Line Executions
41+
- Windows Discovery Techniques
42+
- Active Directory Discovery
43+
asset_type: Endpoint
44+
mitre_attack_id:
45+
- T1119
46+
product:
47+
- Splunk Enterprise
48+
- Splunk Enterprise Security
49+
- Splunk Cloud
50+
category: endpoint
51+
security_domain: endpoint
52+
tests:
53+
- name: True Positive Test
54+
test_type: unit
55+
attack_data:
56+
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1119/windows_dir_piped_to_findstr_activity/snapattack_windows.log
57+
source: XmlWinEventLog:Security
58+
sourcetype: XmlWinEventLog
Lines changed: 58 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
name: Windows Network Sniffing Tools
2+
id: 0c594353-e12d-4867-92f6-2a1b8a1faf5f
3+
version: 1
4+
creation_date: '2026-07-30'
5+
modification_date: '2026-07-30'
6+
author: Raven Tait, Splunk
7+
status: production
8+
type: Anomaly
9+
description: The following analytic detects the execution of common network sniffing tools on Windows systems, including Wireshark, WinPcap, tcpdump, and similar utilities. This activity is significant because attackers use packet capture tools to intercept and analyze network traffic, enabling credential theft, sensitive data harvesting, and reconnaissance of internal network communications. While these tools have legitimate administrative uses, their presence in unexpected environments may indicate an adversary conducting man-in-the-middle attacks or exfiltrating sensitive information traversing the network. If confirmed malicious, this could lead to the exposure of credentials, session tokens, and confidential data, facilitating lateral movement and further compromise of the environment.
10+
data_source:
11+
- Sysmon EventID 1
12+
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process_name IN ("wireshark.exe", "winpcap.exe", "tcpdump", "windump.exe", "netmon.exe", "netcap.exe", "dumpcap.exe", "tshark") by Processes.process Processes.vendor_product Processes.user_id Processes.process_hash Processes.parent_process_name Processes.parent_process_exec Processes.action Processes.dest Processes.process_current_directory Processes.process_path Processes.process_integrity_level Processes.original_file_name Processes.parent_process Processes.parent_process_path Processes.parent_process_guid Processes.parent_process_id Processes.process_guid Processes.process_id Processes.user Processes.process_name | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)`| `security_content_ctime(lastTime)`| `windows_network_sniffing_tools_filter`'
13+
how_to_implement: The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint` data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.
14+
known_false_positives: Legitimate network administrators and security teams may use these tools for authorized network monitoring and troubleshooting. Filter based on approved software inventory and known administrative activity.
15+
references:
16+
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1040/T1040.md
17+
drilldown_searches:
18+
- earliest_offset: $info_min_time$
19+
latest_offset: $info_max_time$
20+
name: View the detection results for - "$user$" and "$dest$"
21+
search: '%original_detection_search% | search user = "$user$" dest = "$dest$"'
22+
- name: View risk events for the last 7 days for - "$user$" and "$dest$"
23+
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user$", "$dest$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
24+
earliest_offset: 7d
25+
latest_offset: '0'
26+
intermediate_findings:
27+
entities:
28+
- field: dest
29+
type: system
30+
score: 20
31+
message: Potential Network Sniffing by $user$ on $dest$ via $process_name$.
32+
threat_objects:
33+
- field: parent_process_name
34+
type: parent_process_name
35+
- field: process_name
36+
type: process_name
37+
analytic_story:
38+
- Credential Dumping
39+
- Data Exfiltration
40+
- Suspicious Command-Line Executions
41+
- Windows Discovery Techniques
42+
- Network Discovery
43+
asset_type: Endpoint
44+
mitre_attack_id:
45+
- T1040
46+
product:
47+
- Splunk Enterprise
48+
- Splunk Enterprise Security
49+
- Splunk Cloud
50+
category: endpoint
51+
security_domain: endpoint
52+
tests:
53+
- name: True Positive Test
54+
test_type: unit
55+
attack_data:
56+
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1040/windows_network_sniffing_tools/snapattack_windows.log
57+
source: XmlWinEventLog:Security
58+
sourcetype: ''
Lines changed: 77 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,77 @@
1+
name: Windows Powershell Commands from DNS TXT
2+
id: b61353cd-5b09-4699-8b86-6517a9038043
3+
version: 1
4+
creation_date: '2026-07-30'
5+
modification_date: '2026-07-30'
6+
author: Raven Tait, Splunk
7+
status: production
8+
type: Anomaly
9+
description: >-
10+
The following analytic detects execution of powershell commands retrieved from
11+
a remote DNS TXT query response. The use of the DNS TXT record for C2 is an uncommon
12+
method for malware that is resilient due to the need for DNS in normal networking
13+
activities. This can ensure that their c2 is not blocked by any firewalls. False
14+
positives are highly unlikely due to the very uncommon chaining of powershell
15+
and DNS TXT queries.
16+
data_source:
17+
- Powershell Script Block Logging 4104
18+
search: |-
19+
`powershell` EventCode=4104
20+
(
21+
(ScriptBlockText="*resolve-dnsname*" AND ScriptBlockText="*-Type TXT*")
22+
OR (ScriptBlockText="*nslookup*" AND ScriptBlockText="*type=txt*")
23+
OR (ScriptBlockText="*dig*" AND ScriptBlockText="* TXT*")
24+
)
25+
(ScriptBlockText="*. (*" OR ScriptBlockText="*IEX*")
26+
| fillnull
27+
| stats count min(_time) as firstTime max(_time) as lastTime
28+
by dest signature signature_id
29+
user_id vendor_product EventID
30+
Guid Opcode Name
31+
Path ProcessID ScriptBlockId
32+
ScriptBlockText
33+
| `security_content_ctime(firstTime)`
34+
| `security_content_ctime(lastTime)`
35+
| `windows_powershell_commands_from_dns_txt_filter`
36+
how_to_implement: To successfully implement this analytic, you will need to enable PowerShell Script Block Logging on some or all endpoints. Additional setup instructions are available at https://docs.splunk.com/Documentation/ES/latest/Admin/Configurepowershelllogging.
37+
known_false_positives: False positives are highly unlikely given the uncommon combination of PowerShell execution and DNS TXT query responses. Legitimate use cases for this behavior are extremely rare and should be investigated thoroughly if detected.
38+
drilldown_searches:
39+
- name: View the detection results for - "$user_id$" and "$dest$"
40+
search: '%original_detection_search% | search user_id = "$user_id$" dest = "$dest$"'
41+
earliest_offset: $info_min_time$
42+
latest_offset: $info_max_time$
43+
- name: View risk events for the last 7 days for - "$user_id$" and "$dest$"
44+
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user_id$", "$dest$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
45+
earliest_offset: 7d
46+
latest_offset: "0"
47+
intermediate_findings:
48+
entities:
49+
- field: dest
50+
type: system
51+
score: 20
52+
message: A suspicious PowerShell script with the ScriptBlockId [$ScriptBlockId$] containing DNS TXT query commands was executed on host $dest$
53+
- field: user_id
54+
type: user
55+
score: 20
56+
message: A suspicious PowerShell script with the ScriptBlockId [$ScriptBlockId$] containing DNS TXT query commands was executed on host $dest$ by user $user_id$
57+
analytic_story:
58+
- Malicious PowerShell
59+
- Command And Control
60+
- Suspicious DNS Traffic
61+
asset_type: Endpoint
62+
mitre_attack_id:
63+
- T1071.004
64+
- T1059.001
65+
product:
66+
- Splunk Enterprise
67+
- Splunk Enterprise Security
68+
- Splunk Cloud
69+
security_domain: endpoint
70+
category: endpoint
71+
tests:
72+
- name: True Positive Test
73+
attack_data:
74+
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1071.004/windows_powershell_commands_from_dns_txt/snapattack_windows.log
75+
source: XmlWinEventLog:Microsoft-Windows-PowerShell/Operational
76+
sourcetype: XmlWinEventLog
77+
test_type: unit
Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,62 @@
1+
name: Windows Suspicious Child of Consent.exe
2+
id: 8194b5d4-41ae-4ce7-adfb-92d375e341d2
3+
version: 1
4+
creation_date: '2026-07-30'
5+
modification_date: '2026-07-30'
6+
author: Raven Tait, Splunk
7+
status: production
8+
type: Anomaly
9+
description: >-
10+
The following analytic detects unexpected child processes spawned by consent.exe,
11+
the Windows UAC consent dialog binary. Consent.exe is responsible solely for
12+
rendering the UAC elevation prompt and should not spawn child processes under
13+
normal operating conditions; child process creation from this parent is a known
14+
indicator of UAC bypass and privilege escalation techniques. The detection identifies
15+
any executable launched as a child of consent.exe, excluding the expected WerFault.exe
16+
error reporting process, which may legitimately appear in crash scenarios. This
17+
behavior is associated with UAC bypass exploits and has been observed in multiple
18+
post-exploitation frameworks as a means of obtaining elevated privileges without
19+
triggering a visible UAC prompt.
20+
data_source:
21+
- Sysmon EventID 1
22+
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes where Processes.process="*.exe*" Processes.parent_process_name="consent.exe" NOT Processes.process="*WerFault.exe*" by Processes.action Processes.dest Processes.original_file_name Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path Processes.process Processes.process_exec Processes.process_guid Processes.process_hash Processes.process_id Processes.process_integrity_level Processes.process_name Processes.process_path Processes.user Processes.user_id Processes.vendor_product | `drop_dm_object_name(Processes)` | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `windows_suspicious_child_of_consent_exe_filter`'
23+
how_to_implement: The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint` data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.
24+
known_false_positives: Legitimate software installations or system updates may occasionally trigger child processes under consent.exe. Verify any flagged activity against known administrative actions or recent software changes.
25+
references:
26+
- https://securelist.com/cve-2024-30051/112618/
27+
drilldown_searches:
28+
- earliest_offset: $info_min_time$
29+
latest_offset: $info_max_time$
30+
name: View the detection results for - "$user$" and "$dest$"
31+
search: '%original_detection_search% | search user = "$user$" dest = "$dest$"'
32+
- name: View risk events for the last 7 days for - "$user$" and "$dest$"
33+
search: '| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user$", "$dest$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
34+
earliest_offset: 7d
35+
latest_offset: '0'
36+
intermediate_findings:
37+
entities:
38+
- field: dest
39+
type: system
40+
score: 20
41+
message: Suspicious Child of Consent.exe activity observed on $dest$.
42+
analytic_story:
43+
- Windows Privilege Escalation
44+
- Unusual Processes
45+
asset_type: Endpoint
46+
mitre_attack_id:
47+
- T1068
48+
- T1548.002
49+
- T1059
50+
product:
51+
- Splunk Enterprise
52+
- Splunk Enterprise Security
53+
- Splunk Cloud
54+
category: endpoint
55+
security_domain: endpoint
56+
tests:
57+
- name: True Positive Test
58+
test_type: unit
59+
attack_data:
60+
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1068/windows_suspicious_child_of_consent_exe/snapattack_windows.log
61+
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
62+
sourcetype: xmlwineventlog

lookups/csv/attacker_tools.csv

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ netpass.exe,This process was identified as malicious by DHS Alert TA18-201A and
2424
NLAChecker.exe,A scanner tool that checks for Windows hosts for Network Level Authentication. This tool allows attackers to detect Windows Servers with RDP without NLA enabled which facilitates the use of brute force non microsoft rdp tools or exploits
2525
NLBrute.exe,A RDP brute force tool found in botnets for further expansion and and acquisition of targets. This process was identified in the SamSam Ransomware Campaign and attackers use this tool to brute force RDP instances with a range of commonly used passwords.
2626
nmap.exe,This process is an open source network mapping tool used to identify hosts and listening services on a network.
27+
netscan.exe,NetScan is a network scanning tool used to discover hosts and services on a network. It is commonly leveraged by threat actors during the discovery phase to enumerate active hosts and open ports within a target environment.
2728
ns.exe,A commonly used tool used by attackers to scan and map file shares
2829
ntdll.exe,This process was identified as malicious by DHS Alert TA18-074A.
2930
OutlookAddressBookView.exe,This process was identified as malicious by DHS Alert TA18-201A and is used by attackers to steal the details of all recipients stored in the address books of Microsoft Outlook.

0 commit comments

Comments
 (0)