Add detection for suspicious WMI-based lateral movement - #1
Open
cyber20233 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
This PR adds a new Windows process creation rule to detect suspicious command shell or PowerShell execution spawned by wmiprvse.exe with encoded or reconnaissance commands.
This behavior may indicate WMI-based lateral movement, such as Impacket wmiexec-style execution, where commands are executed remotely without dropping binaries.
The rule complements existing WMI-related detections by focusing on process creation behavior rather than WMI event logging.
Changelog
new: Suspicious PowerShell or CMD Spawned by WMI Provider with Encoded or Recon Commands
Example Log Event
N/A
Fixed Issues
N/A
SigmaHQ Rule Creation Conventions