Closed
Conversation
nursery/persist-via-pendingfilerenameoperations-registry-value.yml
Outdated
Show resolved
Hide resolved
Collaborator
|
This appears to be a duplicate of #1132. Closing this issue in favor of the former. |
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
3 participants
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
Adds a new nursery rule to detect persistence via the PendingFileRenameOperations registry value under the Windows Session Manager.
Closes: #911
What Changed
Added a rule:
rules/nursery/persist-via-pendingfilerenameoperations-registry-value.yml
The rule detects when malware sets:
HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
This registry value is commonly abused to schedule file rename/delete operations that execute on the next system reboot.
Validation
capafmt passed, lint --thorough passed
Notes
Added as a nursery rule for further testing and feedback.
It allows capa to identify programs that schedule malicious file operations to run after a system reboot.