First Time Seen Commonly Abused Remote Access Tool Execution

  1[metadata]
  2creation_date = "2023/04/03"
  3integration = ["endpoint", "windows"]
  4maturity = "production"
  5updated_date = "2024/08/07"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Adversaries may install legitimate remote access tools (RAT) to compromised endpoints for further command-and-control
 11(C2). Adversaries can rely on installed RATs for persistence, execution of native commands and more. This rule detects
 12when a process is started whose name or code signature resembles commonly abused RATs. This is a New Terms rule type
 13indicating the host has not seen this RAT process started before within the last 30 days.
 14"""
 15from = "now-9m"
 16index = [
 17    "logs-endpoint.events.process-*",
 18    "endgame-*",
 19    "winlogbeat-*",
 20    "logs-windows.*",
 21    "logs-system.security*",
 22]
 23language = "kuery"
 24license = "Elastic License v2"
 25name = "First Time Seen Commonly Abused Remote Access Tool Execution"
 26note = """## Triage and analysis
 27
 28### Investigating First Time Seen Commonly Abused Remote Access Tool Execution
 29
 30Remote access software is a class of tools commonly used by IT departments to provide support by connecting securely to users' computers. Remote access is an ever-growing market where new companies constantly offer new ways of quickly accessing remote systems.
 31
 32At the same pace as IT departments adopt these tools, the attackers also adopt them as part of their workflow to connect into an interactive session, maintain access with legitimate software as a persistence mechanism, drop malicious software, etc.
 33
 34This rule detects when a remote access tool is seen in the environment for the first time in the last 15 days, enabling analysts to investigate and enforce the correct usage of such tools.
 35
 36#### Possible investigation steps
 37
 38- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 39- Check if the execution of the remote access tool is approved by the organization's IT department.
 40- Investigate other alerts associated with the user/host during the past 48 hours.
 41- Contact the account owner and confirm whether they are aware of this activity.
 42  - If the tool is not approved for use in the organization, the employee could have been tricked into installing it and providing access to a malicious third party. Investigate whether this third party could be attempting to scam the end-user or gain access to the environment through social engineering.
 43- Investigate any abnormal behavior by the subject process, such as network connections, registry or file modifications, and any spawned child processes.
 44
 45### False positive analysis
 46
 47- If an authorized support person or administrator used the tool to conduct legitimate support or remote access, consider reinforcing that only tooling approved by the IT policy should be used. The analyst can dismiss the alert if no other suspicious behavior is observed involving the host or users.
 48
 49### Response and remediation
 50
 51- Initiate the incident response process based on the outcome of the triage.
 52- Isolate the involved host to prevent further post-compromise behavior.
 53- Run a full scan using the antimalware tool in place. This scan can reveal additional artifacts left in the system, persistence mechanisms, and malware components.
 54- Investigate credential exposure on systems compromised or used by the attacker to ensure all compromised accounts are identified. Reset passwords for these accounts and other potentially compromised credentials, such as email, business systems, and web services.
 55- If an unauthorized third party did the access via social engineering, consider improvements to the security awareness program.
 56- Enforce that only tooling approved by the IT policy should be used for remote access purposes and only by authorized staff.
 57- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 58"""
 59references = [
 60    "https://thedfirreport.com/2023/04/03/malicious-iso-file-leads-to-domain-wide-ransomware/",
 61    "https://attack.mitre.org/techniques/T1219/",
 62    "https://github.com/redcanaryco/surveyor/blob/master/definitions/remote-admin.json",
 63]
 64risk_score = 47
 65rule_id = "6e1a2cc4-d260-11ed-8829-f661ea17fbcc"
 66severity = "medium"
 67tags = [
 68    "Domain: Endpoint",
 69    "OS: Windows",
 70    "Use Case: Threat Detection",
 71    "Tactic: Command and Control",
 72    "Resources: Investigation Guide",
 73    "Data Source: Elastic Defend",
 74    "Data Source: Elastic Endgame",
 75    "Data Source: System",
 76]
 77timestamp_override = "event.ingested"
 78type = "new_terms"
 79
 80query = '''
 81host.os.type: "windows" and
 82
 83   event.category: "process" and event.type : "start" and
 84
 85    (
 86        process.code_signature.subject_name : (
 87            "Action1 Corporation" or
 88            "AeroAdmin LLC" or
 89            "Ammyy LLC" or
 90            "Atera Networks Ltd" or
 91            "AWERAY PTE. LTD." or
 92            "BeamYourScreen GmbH" or
 93            "Bomgar Corporation" or
 94            "DUC FABULOUS CO.,LTD" or
 95            "DOMOTZ INC." or
 96            "DWSNET OÜ" or
 97            "FleetDeck Inc" or
 98            "GlavSoft LLC" or
 99            "GlavSoft LLC." or
100            "Hefei Pingbo Network Technology Co. Ltd" or
101            "IDrive, Inc." or
102            "IMPERO SOLUTIONS LIMITED" or
103            "Instant Housecall" or
104            "ISL Online Ltd." or
105            "LogMeIn, Inc." or
106            "Monitoring Client" or
107            "MMSOFT Design Ltd." or
108            "Nanosystems S.r.l." or
109            "NetSupport Ltd" or
110            "NinjaRMM, LLC" or
111            "Parallels International GmbH" or
112            "philandro Software GmbH" or
113            "Pro Softnet Corporation" or
114            "RealVNC" or
115            "RealVNC Limited" or
116            "BreakingSecurity.net" or
117            "Remote Utilities LLC" or
118            "Rocket Software, Inc." or
119            "SAFIB" or
120            "Servably, Inc." or
121            "ShowMyPC INC" or
122            "Splashtop Inc." or
123            "Superops Inc." or
124            "TeamViewer" or
125            "TeamViewer GmbH" or
126            "TeamViewer Germany GmbH" or
127            "Techinline Limited" or
128            "uvnc bvba" or
129            "Yakhnovets Denis Aleksandrovich IP" or
130            "Zhou Huabing"
131        ) or
132
133        process.name.caseless : (
134            AA_v*.exe or
135            "AeroAdmin.exe" or
136            "AnyDesk.exe" or
137            "apc_Admin.exe" or
138            "apc_host.exe" or
139            "AteraAgent.exe" or
140            aweray_remote*.exe or
141            "AweSun.exe" or
142            "B4-Service.exe" or
143            "BASupSrvc.exe" or
144            "bomgar-scc.exe" or
145            "domotzagent.exe" or
146            "domotz-windows-x64-10.exe" or
147            "dwagsvc.exe" or
148            "DWRCC.exe" or
149            "ImperoClientSVC.exe" or
150            "ImperoServerSVC.exe" or
151            "ISLLight.exe" or
152            "ISLLightClient.exe" or
153            fleetdeck_commander*.exe or
154            "getscreen.exe" or
155            "LMIIgnition.exe" or
156            "LogMeIn.exe" or
157            "ManageEngine_Remote_Access_Plus.exe" or
158            "Mikogo-Service.exe" or
159            "NinjaRMMAgent.exe" or
160            "NinjaRMMAgenPatcher.exe" or
161            "ninjarmm-cli.exe" or
162            "r_server.exe" or
163            "radmin.exe" or
164            "radmin3.exe" or
165            "RCClient.exe" or
166            "RCService.exe" or
167            "RemoteDesktopManager.exe" or
168            "RemotePC.exe" or
169            "RemotePCDesktop.exe" or
170            "RemotePCService.exe" or
171            "rfusclient.exe" or
172            "ROMServer.exe" or
173            "ROMViewer.exe" or
174            "RPCSuite.exe" or
175            "rserver3.exe" or
176            "rustdesk.exe" or
177            "rutserv.exe" or
178            "rutview.exe" or
179            "saazapsc.exe" or
180            ScreenConnect*.exe or
181            "smpcview.exe" or
182            "spclink.exe" or
183            "Splashtop-streamer.exe" or
184            "SRService.exe" or
185            "strwinclt.exe" or
186            "Supremo.exe" or
187            "SupremoService.exe" or
188            "teamviewer.exe" or
189            "TiClientCore.exe" or
190            "TSClient.exe" or
191            "tvn.exe" or
192            "tvnserver.exe" or
193            "tvnviewer.exe" or
194            UltraVNC*.exe or
195            UltraViewer*.exe or
196            "vncserver.exe" or
197            "vncviewer.exe" or
198            "winvnc.exe" or
199            "winwvc.exe" or
200            "Zaservice.exe" or
201            "ZohoURS.exe"
202        ) or
203        process.name : (
204            AA_v*.exe or
205            "AeroAdmin.exe" or
206            "AnyDesk.exe" or
207            "apc_Admin.exe" or
208            "apc_host.exe" or
209            "AteraAgent.exe" or
210            aweray_remote*.exe or
211            "AweSun.exe" or
212            "B4-Service.exe" or
213            "BASupSrvc.exe" or
214            "bomgar-scc.exe" or
215            "domotzagent.exe" or
216            "domotz-windows-x64-10.exe" or
217            "dwagsvc.exe" or
218            "DWRCC.exe" or
219            "ImperoClientSVC.exe" or
220            "ImperoServerSVC.exe" or
221            "ISLLight.exe" or
222            "ISLLightClient.exe" or
223            fleetdeck_commander*.exe or
224            "getscreen.exe" or
225            "LMIIgnition.exe" or
226            "LogMeIn.exe" or
227            "ManageEngine_Remote_Access_Plus.exe" or
228            "Mikogo-Service.exe" or
229            "NinjaRMMAgent.exe" or
230            "NinjaRMMAgenPatcher.exe" or
231            "ninjarmm-cli.exe" or
232            "r_server.exe" or
233            "radmin.exe" or
234            "radmin3.exe" or
235            "RCClient.exe" or
236            "RCService.exe" or
237            "RemoteDesktopManager.exe" or
238            "RemotePC.exe" or
239            "RemotePCDesktop.exe" or
240            "RemotePCService.exe" or
241            "rfusclient.exe" or
242            "ROMServer.exe" or
243            "ROMViewer.exe" or
244            "RPCSuite.exe" or
245            "rserver3.exe" or
246            "rustdesk.exe" or
247            "rutserv.exe" or
248            "rutview.exe" or
249            "saazapsc.exe" or
250            ScreenConnect*.exe or
251            "smpcview.exe" or
252            "spclink.exe" or
253            "Splashtop-streamer.exe" or
254            "SRService.exe" or
255            "strwinclt.exe" or
256            "Supremo.exe" or
257            "SupremoService.exe" or
258            "teamviewer.exe" or
259            "TiClientCore.exe" or
260            "TSClient.exe" or
261            "tvn.exe" or
262            "tvnserver.exe" or
263            "tvnviewer.exe" or
264            UltraVNC*.exe or
265            UltraViewer*.exe or
266            "vncserver.exe" or
267            "vncviewer.exe" or
268            "winvnc.exe" or
269            "winwvc.exe" or
270            "Zaservice.exe" or
271            "ZohoURS.exe"
272        )
273	) and
274
275	not (process.pe.original_file_name : ("G2M.exe" or "Updater.exe" or "powershell.exe") and process.code_signature.subject_name : "LogMeIn, Inc.")
276'''
277
278
279[[rule.threat]]
280framework = "MITRE ATT&CK"
281[[rule.threat.technique]]
282id = "T1219"
283name = "Remote Access Software"
284reference = "https://attack.mitre.org/techniques/T1219/"
285
286
287[rule.threat.tactic]
288id = "TA0011"
289name = "Command and Control"
290reference = "https://attack.mitre.org/tactics/TA0011/"
291
292[rule.new_terms]
293field = "new_terms_fields"
294value = ["host.id"]
295[[rule.new_terms.history_window_start]]
296field = "history_window_start"
297value = "now-15d"