Skip to content

Commit b7b7084

Browse files
authored
Merge pull request #3621 from splunk/interlock_ransomware
interlock_ransomware
2 parents 6ac8e21 + 968d460 commit b7b7084

File tree

44 files changed

+1061
-787
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+1061
-787
lines changed

detections/endpoint/common_ransomware_extensions.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
name: Common Ransomware Extensions
22
id: a9e5c5db-db11-43ca-86a8-c852d1b2c0ec
3-
version: 14
4-
date: '2025-05-02'
3+
version: 15
4+
date: '2025-07-29'
55
author: David Dorsey, Michael Haag, Splunk, Steven Dick
66
status: production
77
type: TTP
@@ -79,6 +79,8 @@ tags:
7979
- Ryuk Ransomware
8080
- Black Basta Ransomware
8181
- Termite Ransomware
82+
- Interlock Ransomware
83+
- NailaoLocker Ransomware
8284
asset_type: Endpoint
8385
mitre_attack_id:
8486
- T1485

detections/endpoint/common_ransomware_notes.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
name: Common Ransomware Notes
22
id: ada0f478-84a8-4641-a3f1-d82362d6bd71
3-
version: 10
4-
date: '2025-05-02'
3+
version: 11
4+
date: '2025-07-29'
55
author: David Dorsey, Splunk
66
status: production
77
type: Hunting
@@ -42,6 +42,8 @@ tags:
4242
- Ryuk Ransomware
4343
- Black Basta Ransomware
4444
- Termite Ransomware
45+
- Interlock Ransomware
46+
- NailaoLocker Ransomware
4547
asset_type: Endpoint
4648
mitre_attack_id:
4749
- T1485

detections/endpoint/detect_remote_access_software_usage_file.yml

Lines changed: 31 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
name: Detect Remote Access Software Usage File
22
id: 3bf5541a-6a45-4fdc-b01d-59b899fff961
3-
version: 9
4-
date: '2025-05-02'
3+
version: 10
4+
date: '2025-07-28'
55
author: Steven Dick
66
status: production
77
type: Anomaly
8-
description: The following analytic detects the writing of files from known remote
9-
access software to disk within the environment. It leverages data from Endpoint
10-
Detection and Response (EDR) agents, focusing on file path, file name, and user
11-
information. This activity is significant as adversaries often use remote access
12-
tools like AnyDesk, GoToMyPC, LogMeIn, and TeamViewer to maintain unauthorized access.
13-
If confirmed malicious, this could allow attackers to persist in the environment,
14-
potentially leading to data exfiltration, further compromise, or complete control
15-
over affected systems.
8+
description: The following analytic detects the writing of files from known
9+
remote access software to disk within the environment. It leverages data from
10+
Endpoint Detection and Response (EDR) agents, focusing on file path, file
11+
name, and user information. This activity is significant as adversaries often
12+
use remote access tools like AnyDesk, GoToMyPC, LogMeIn, and TeamViewer to
13+
maintain unauthorized access. If confirmed malicious, this could allow
14+
attackers to persist in the environment, potentially leading to data
15+
exfiltration, further compromise, or complete control over affected systems.
1616
data_source:
1717
- Sysmon EventID 11
1818
search: '| tstats `security_content_summariesonly` count, min(_time) as firstTime,
@@ -25,20 +25,22 @@ search: '| tstats `security_content_summariesonly` count, min(_time) as firstTim
2525
remote_access_software remote_utility AS file_name OUTPUT isutility, description
2626
as signature, comment_reference as desc, category | search isutility = TRUE | `remote_access_software_usage_exceptions`
2727
| `detect_remote_access_software_usage_file_filter`'
28-
how_to_implement: The detection is based on data that originates from Endpoint Detection
29-
and Response (EDR) agents. These agents are designed to provide security-related
30-
telemetry from the endpoints where the agent is installed. To implement this search,
31-
you must ingest logs that contain the file path, file name, and the user that created
32-
the file. These logs must be processed using the appropriate Splunk Technology Add-ons
33-
that are specific to the EDR product. The logs must also be mapped to the `Filesystem`
34-
node of the `Endpoint` data model. Use the Splunk Common Information Model (CIM)
35-
to normalize the field names and speed up the data modeling process. The "exceptions"
36-
macro leverages both an Assets and Identities lookup, as well as a KVStore collection
37-
called "remote_software_exceptions" that lets you track and maintain device-based
38-
exceptions for this set of detections.
39-
known_false_positives: Known or approved applications used by the organization or
40-
usage of built-in functions. Known false positives can be added to the remote_access_software_usage_exception.csv
41-
lookup to globally suppress these situations across all remote access content
28+
how_to_implement: The detection is based on data that originates from Endpoint
29+
Detection and Response (EDR) agents. These agents are designed to provide
30+
security-related telemetry from the endpoints where the agent is installed. To
31+
implement this search, you must ingest logs that contain the file path, file
32+
name, and the user that created the file. These logs must be processed using
33+
the appropriate Splunk Technology Add-ons that are specific to the EDR
34+
product. The logs must also be mapped to the `Filesystem` node of the
35+
`Endpoint` data model. Use the Splunk Common Information Model (CIM) to
36+
normalize the field names and speed up the data modeling process. The
37+
"exceptions" macro leverages both an Assets and Identities lookup, as well as
38+
a KVStore collection called "remote_software_exceptions" that lets you track
39+
and maintain device-based exceptions for this set of detections.
40+
known_false_positives: Known or approved applications used by the organization
41+
or usage of built-in functions. Known false positives can be added to the
42+
remote_access_software_usage_exception.csv lookup to globally suppress these
43+
situations across all remote access content
4244
references:
4345
- https://attack.mitre.org/techniques/T1219/
4446
- https://thedfirreport.com/2022/08/08/bumblebee-roasts-its-way-to-domain-admin/
@@ -62,8 +64,8 @@ drilldown_searches:
6264
earliest_offset: $info_min_time$
6365
latest_offset: $info_max_time$
6466
rba:
65-
message: A file for known a remote access software [$file_name$] was created on
66-
$dest$ by $user$.
67+
message: A file for known a remote access software [$file_name$] was created
68+
on $dest$ by $user$.
6769
risk_objects:
6870
- field: dest
6971
type: system
@@ -86,6 +88,7 @@ tags:
8688
- Remote Monitoring and Management Software
8789
- Cactus Ransomware
8890
- Seashell Blizzard
91+
- Interlock Ransomware
8992
asset_type: Endpoint
9093
mitre_attack_id:
9194
- T1219
@@ -98,6 +101,7 @@ tags:
98101
tests:
99102
- name: True Positive Test
100103
attack_data:
101-
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
104+
- data:
105+
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
102106
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
103107
sourcetype: XmlWinEventLog

detections/endpoint/detect_remote_access_software_usage_fileinfo.yml

Lines changed: 25 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,18 @@
11
name: Detect Remote Access Software Usage FileInfo
22
id: ccad96d7-a48c-4f13-8b9c-9f6a31cba454
3-
version: 9
4-
date: '2025-05-02'
3+
version: 10
4+
date: '2025-07-28'
55
author: Steven Dick
66
status: production
77
type: Anomaly
8-
description: The following analytic detects the execution of processes with file or
9-
code signing attributes from known remote access software within the environment.
10-
It leverages Sysmon EventCode 1 data and cross-references a lookup table of remote
11-
access utilities such as AnyDesk, GoToMyPC, LogMeIn, and TeamViewer. This activity
12-
is significant as adversaries often use these tools to maintain unauthorized remote
13-
access. If confirmed malicious, this could allow attackers to persist in the environment,
14-
potentially leading to data exfiltration or further compromise of the network.
8+
description: The following analytic detects the execution of processes with file
9+
or code signing attributes from known remote access software within the
10+
environment. It leverages Sysmon EventCode 1 data and cross-references a
11+
lookup table of remote access utilities such as AnyDesk, GoToMyPC, LogMeIn,
12+
and TeamViewer. This activity is significant as adversaries often use these
13+
tools to maintain unauthorized remote access. If confirmed malicious, this
14+
could allow attackers to persist in the environment, potentially leading to
15+
data exfiltration or further compromise of the network.
1516
data_source:
1617
- Sysmon EventID 1
1718
search: '`sysmon` EventCode=1 | stats count min(_time) as firstTime max(_time) as
@@ -22,14 +23,16 @@ search: '`sysmon` EventCode=1 | stats count min(_time) as firstTime max(_time) a
2223
remote_utility_fileinfo AS Product OUTPUT isutility, description as signature, comment_reference
2324
as desc, category | search isutility = True | `remote_access_software_usage_exceptions`
2425
| `detect_remote_access_software_usage_fileinfo_filter`'
25-
how_to_implement: This analytic relies on Sysmon to be properly installed and utilized
26-
in the environment. Ensure that proper logging is setup for Sysmon and data is being
27-
ingested into Splunk. The "exceptions" macro leverages both an Assets and Identities
28-
lookup, as well as a KVStore collection named "remote_software_exceptions" that
29-
lets you track and maintain device-based exceptions for this set of detections.
30-
known_false_positives: Known or approved applications used by the organization or
31-
usage of built-in functions. Known false positives can be added to the remote_access_software_usage_exception.csv
32-
lookup to globally suppress these situations across all remote access content
26+
how_to_implement: This analytic relies on Sysmon to be properly installed and
27+
utilized in the environment. Ensure that proper logging is setup for Sysmon
28+
and data is being ingested into Splunk. The "exceptions" macro leverages both
29+
an Assets and Identities lookup, as well as a KVStore collection named
30+
"remote_software_exceptions" that lets you track and maintain device-based
31+
exceptions for this set of detections.
32+
known_false_positives: Known or approved applications used by the organization
33+
or usage of built-in functions. Known false positives can be added to the
34+
remote_access_software_usage_exception.csv lookup to globally suppress these
35+
situations across all remote access content
3336
references:
3437
- https://attack.mitre.org/techniques/T1219/
3538
- https://thedfirreport.com/2022/08/08/bumblebee-roasts-its-way-to-domain-admin/
@@ -53,8 +56,8 @@ drilldown_searches:
5356
earliest_offset: $info_min_time$
5457
latest_offset: $info_max_time$
5558
rba:
56-
message: A file attributes for known a remote access software [$process_name$] was
57-
detected on $dest$
59+
message: A file attributes for known a remote access software [$process_name$]
60+
was detected on $dest$
5861
risk_objects:
5962
- field: dest
6063
type: system
@@ -76,6 +79,7 @@ tags:
7679
- Remote Monitoring and Management Software
7780
- Cactus Ransomware
7881
- Seashell Blizzard
82+
- Interlock Ransomware
7983
asset_type: Endpoint
8084
mitre_attack_id:
8185
- T1219
@@ -88,6 +92,7 @@ tags:
8892
tests:
8993
- name: True Positive Test
9094
attack_data:
91-
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
95+
- data:
96+
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
9297
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
9398
sourcetype: XmlWinEventLog

detections/endpoint/detect_remote_access_software_usage_process.yml

Lines changed: 39 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,20 @@
11
name: Detect Remote Access Software Usage Process
22
id: ffd5e001-2e34-48f4-97a2-26dc4bb08178
3-
version: 9
4-
date: '2025-05-02'
3+
version: 10
4+
date: '2025-07-28'
55
author: Steven Dick, Sebastian Wurl, Splunk Community
66
status: production
77
type: Anomaly
8-
description: The following analytic detects the execution of known remote access software
9-
within the environment. It leverages data from Endpoint Detection and Response (EDR)
10-
agents, focusing on process names and parent processes mapped to the Endpoint data
11-
model. We then compare with with a list of known remote access software shipped as a lookup file - remote_access_software. This activity is significant as adversaries often use remote access tools like AnyDesk, GoToMyPC, LogMeIn, and TeamViewer to maintain unauthorized access.
12-
If confirmed malicious, this could allow attackers to control systems remotely,
13-
exfiltrate data, or deploy additional malware, posing a severe threat to the organization's
14-
security.
8+
description: The following analytic detects the execution of known remote access
9+
software within the environment. It leverages data from Endpoint Detection and
10+
Response (EDR) agents, focusing on process names and parent processes mapped
11+
to the Endpoint data model. We then compare with with a list of known remote
12+
access software shipped as a lookup file - remote_access_software. This
13+
activity is significant as adversaries often use remote access tools like
14+
AnyDesk, GoToMyPC, LogMeIn, and TeamViewer to maintain unauthorized access. If
15+
confirmed malicious, this could allow attackers to control systems remotely,
16+
exfiltrate data, or deploy additional malware, posing a severe threat to the
17+
organization's security.
1518
data_source:
1619
- Sysmon EventID 1
1720
- Windows Event Log Security 4688
@@ -33,22 +36,25 @@ search: |
3336
| search isutility = TRUE
3437
| `remote_access_software_usage_exceptions`
3538
| `detect_remote_access_software_usage_process_filter`
36-
how_to_implement: The detection is based on data that originates from Endpoint Detection
37-
and Response (EDR) agents. These agents are designed to provide security-related
38-
telemetry from the endpoints where the agent is installed. To implement this search,
39-
you must ingest logs that contain the process GUID, process name, and parent process.
40-
Additionally, you must ingest complete command-line executions. These logs must
41-
be processed using the appropriate Splunk Technology Add-ons that are specific to
42-
the EDR product. The logs must also be mapped to the `Processes` node of the `Endpoint`
43-
data model. Use the Splunk Common Information Model (CIM) to normalize the field
44-
names and speed up the data modeling process. The "exceptions" macro leverages both
45-
an Assets and Identities lookup, as well as a KVStore collection called "remote_software_exceptions"
46-
that lets you track and maintain device- based exceptions for this set of detections.
47-
known_false_positives: It is possible that legitimate remote access software is used
48-
within the environment. Ensure that the lookup is reviewed and updated with any
49-
additional remote access software that is used within the environment. Known false
50-
positives can be added to the remote_access_software_usage_exception.csv lookup
51-
to globally suppress these situations across all remote access content
39+
how_to_implement: The detection is based on data that originates from Endpoint
40+
Detection and Response (EDR) agents. These agents are designed to provide
41+
security-related telemetry from the endpoints where the agent is installed. To
42+
implement this search, you must ingest logs that contain the process GUID,
43+
process name, and parent process. Additionally, you must ingest complete
44+
command-line executions. These logs must be processed using the appropriate
45+
Splunk Technology Add-ons that are specific to the EDR product. The logs must
46+
also be mapped to the `Processes` node of the `Endpoint` data model. Use the
47+
Splunk Common Information Model (CIM) to normalize the field names and speed
48+
up the data modeling process. The "exceptions" macro leverages both an Assets
49+
and Identities lookup, as well as a KVStore collection called
50+
"remote_software_exceptions" that lets you track and maintain device- based
51+
exceptions for this set of detections.
52+
known_false_positives: It is possible that legitimate remote access software is
53+
used within the environment. Ensure that the lookup is reviewed and updated
54+
with any additional remote access software that is used within the
55+
environment. Known false positives can be added to the
56+
remote_access_software_usage_exception.csv lookup to globally suppress these
57+
situations across all remote access content
5258
references:
5359
- https://attack.mitre.org/techniques/T1219/
5460
- https://thedfirreport.com/2022/08/08/bumblebee-roasts-its-way-to-domain-admin/
@@ -72,8 +78,8 @@ drilldown_searches:
7278
earliest_offset: $info_min_time$
7379
latest_offset: $info_max_time$
7480
rba:
75-
message: A process for a known remote access software $process_name$ was identified
76-
on $dest$.
81+
message: A process for a known remote access software $process_name$ was
82+
identified on $dest$.
7783
risk_objects:
7884
- field: dest
7985
type: system
@@ -96,6 +102,7 @@ tags:
96102
- Remote Monitoring and Management Software
97103
- Cactus Ransomware
98104
- Seashell Blizzard
105+
- Interlock Ransomware
99106
asset_type: Endpoint
100107
mitre_attack_id:
101108
- T1219
@@ -108,9 +115,11 @@ tags:
108115
tests:
109116
- name: True Positive Test
110117
attack_data:
111-
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
118+
- data:
119+
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/screenconnect/screenconnect_sysmon.log
112120
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
113121
sourcetype: XmlWinEventLog
114-
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/atomic_red_team/windows-sysmon.log
122+
- data:
123+
https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1219/atomic_red_team/windows-sysmon.log
115124
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational
116-
sourcetype: XmlWinEventLog
125+
sourcetype: XmlWinEventLog

0 commit comments

Comments
 (0)