Files
blue-team-tools/rules/windows/process_creation/proc_creation_win_virtualbox_execution.yml
T
frack113 020fc8061f Merge PR #4479 From @frack113 - Upgrade Rules Status
chore: Upgrade status level from `experimental` to `test` for rules that have not changed in 300 days

---------

Signed-off-by: frack113 <62423083+frack113@users.noreply.github.com>
Co-authored-by: nasbench <8741929+nasbench@users.noreply.github.com>
2023-10-17 14:35:26 +02:00

37 lines
1.2 KiB
YAML

title: Detect Virtualbox Driver Installation OR Starting Of VMs
id: bab049ca-7471-4828-9024-38279a4c04da
status: test
description: Adversaries can carry out malicious operations using a virtual instance to avoid detection. This rule is built to detect the registration of the Virtualbox driver or start of a Virtualbox VM.
references:
- https://news.sophos.com/en-us/2020/05/21/ragnar-locker-ransomware-deploys-virtual-machine-to-dodge-security/
- https://threatpost.com/maze-ransomware-ragnar-locker-virtual-machine/159350/
author: Janantha Marasinghe
date: 2020/09/26
modified: 2022/07/14
tags:
- attack.defense_evasion
- attack.t1564.006
- attack.t1564
logsource:
category: process_creation
product: windows
detection:
selection_1:
CommandLine|contains:
- 'VBoxRT.dll,RTR3Init'
- 'VBoxC.dll'
- 'VBoxDrv.sys'
selection_2:
CommandLine|contains:
- 'startvm'
- 'controlvm'
condition: 1 of selection_*
fields:
- ComputerName
- User
- CommandLine
- ParentCommandLine
falsepositives:
- This may have false positives on hosts where Virtualbox is legitimately being used for operations
level: low