Skip to content

fix(rules): Use ps.name field in Macro execution via script interpreter rule #500

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.

Sign up for GitHub

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

Merged
rabbitstack merged 1 commit into from
Apr 30, 2025
Merged

fix(rules): Use ps.name field in Macro execution via script interpreter rule #500

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions rules/initial_access_macro_execution_via_script_interpreter.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
name: Macro execution via script interpreter
id: 845404de-df6f-472f-bd74-72148a7f5166
version: 1.0.2
version: 1.0.3
description: |
Identifies the execution of the Windows scripting interpreter spawning
a Microsoft Office process to execute suspicious Visual Basic macro.
Expand All @@ -18,7 +18,7 @@ labels:
condition: >
sequence
maxspan 5m
|spawn_process and ps.parent.name iin script_interpreters and ps.child.name iin msoffice_binaries| by ps.child.uuid
|spawn_process and ps.name iin script_interpreters and ps.child.name iin msoffice_binaries| by ps.child.uuid
|ps.name iin msoffice_binaries and thread.callstack.modules imatches '*vbe?.dll'
and
(spawn_process or (create_remote_thread) or (modify_registry) or (create_file)
Expand Down