Files
hayabusa/rules/Sigma/win_susp_use_of_vsjitdebugger_bin.yml
2021-11-14 11:00:56 +09:00

40 lines
1.5 KiB
YAML

title: Malicious PE Execution by Microsoft Visual Studio Debugger
author: "Agro (@agro_sev), Ensar \u015Eamil (@sblmsrsn), oscd.community"
date: 2020/10/14
description: There is an option for a MS VS Just-In-Time Debugger "vsjitdebugger.exe"
to launch specified executable and attach a debugger. This option may be used
adversaries to execute malicious code by signed verified binary. The debugger
is installed alongside with Microsoft Visual Studio package.
detection:
SELECTION_1:
EventID: 1
SELECTION_2:
ParentImage: '*\vsjitdebugger.exe'
SELECTION_3:
EventID: 1
SELECTION_4:
Image: '*\vsimmersiveactivatehelper*.exe'
SELECTION_5:
Image: '*\devenv.exe'
condition: (SELECTION_1 and SELECTION_2 and not ((SELECTION_3 and (SELECTION_4
or SELECTION_5))))
falsepositives:
- the process spawned by vsjitdebugger.exe is uncommon.
id: 15c7904e-6ad1-4a45-9b46-5fb25df37fd2
level: medium
logsource:
category: process_creation
product: windows
modified: 2021/07/06
references:
- https://twitter.com/pabraeken/status/990758590020452353
- https://github.com/LOLBAS-Project/LOLBAS/blob/master/yml/OtherMSBinaries/Vsjitdebugger.yml
- https://docs.microsoft.com/en-us/visualstudio/debugger/debug-using-the-just-in-time-debugger?view=vs-2019
status: experimental
tags:
- attack.t1218
- attack.defense_evasion
yml_filename: win_susp_use_of_vsjitdebugger_bin.yml
yml_path: /Users/user/Documents/YamatoSecurity/sigma/rules/windows/process_creation