New Rule : PowerShell Console History File Access - proc_creation#5253
Merged
phantinuss merged 12 commits intoSigmaHQ:masterfrom Sep 22, 2025
Merged
New Rule : PowerShell Console History File Access - proc_creation#5253phantinuss merged 12 commits intoSigmaHQ:masterfrom
phantinuss merged 12 commits intoSigmaHQ:masterfrom
Conversation
nasbench
requested changes
Apr 16, 2025
Contributor
Author
|
Rule updated @nasbench |
phantinuss
approved these changes
Jun 25, 2025
…nsole_history_file_access.yml Co-authored-by: phantinuss <79651203+phantinuss@users.noreply.github.com>
…nsole_history_file_access.yml Co-authored-by: phantinuss <79651203+phantinuss@users.noreply.github.com>
…nsole_history_file_access.yml Co-authored-by: phantinuss <79651203+phantinuss@users.noreply.github.com>
…nsole_history_file_access.yml
swachchhanda000
approved these changes
Sep 5, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new Sigma detection rule to identify potential unauthorized access to PowerShell console history files, which can contain sensitive information like plaintext passwords. The rule targets attempts to read the ConsoleHost_history.txt file or retrieve its path.
- Adds detection for PowerShell console history file access attempts
- Covers both direct file access and path retrieval methods
- Targets credential access techniques used by red teams for reconnaissance
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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
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
Add a new rule concerning access to the PowerShell console history file.
A red team has been seen using this technique with the following command
cmd.exe /q /c powershell.exe "type C:\Users\*\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt" > output_filein order to try to retrieve plaintext passwords that may have been used in PowerShell commands.Changelog
new: Potential PowerShell Console History File Access Attempt
Example Log Event
Fixed Issues
SigmaHQ Rule Creation Conventions