-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add enumerate-blocking-processes.yml #705
Conversation
The AVOSLOCKER ransomware uses the APIs `RmRegisterResources` and `RmGetList` to get a list of processes blocking the file to encrypt and stop them.
examples: | ||
- 43b7a60c0ef8b4af001f45a0c57410b7374b1d75a6811e0dfc86e4d60f503856:0x402C5E |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add this to the testfiles or remove here?
@@ -0,0 +1,17 @@ | |||
rule: | |||
meta: | |||
name: enumerate blocking processes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this name isn't super descriptive to me: its not clear what the process is blocking. would you at least add a description that explains what this is?
- api: RmRegisterResources | ||
- api: RmGetList |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
recommend adding the DLL name to be explicit, but not required
Co-authored-by: Willi Ballenthin <[email protected]>
move to nursery
Thanks, @Ana06! |
The AVOSLOCKER ransomware uses the APIs
RmRegisterResources
andRmGetList
to get a list of processes blocking the file to encrypt and stop them.