-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Contribute Sigma Rules from Personal Repository to Main Sigma Repository #4961
Conversation
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.
Welcome @tsale 👋
It looks like this is your first pull request on the Sigma rules repository!
Please make sure to read the SigmaHQ conventions document to make sure your contribution is adhering to best practices and has all the necessary elements in place for a successful approval.
Thanks again, and welcome to the Sigma community! 😃
Thanks @tsale for this huge contribution. I'll get to reviewing and get back to you with any comments (if necessary). |
Now you've broken all my work! @tsale 😢 please revert the commit |
I'm still working on this so i'll be reverting ba843fb. Cuz i already did all the changes and more. |
Oops sorry about that, lol. I reverted the commit and then I saw you made another comment below 😆 |
This PR introduces a set of Sigma rules originally published in my personal repository (https://github.com/tsale/Sigma_rules). The project was created to include unique rules based on my research, specifically targeting gaps in the open-source community. At the time of their creation, no similar rules were found in the main Sigma repository or elsewhere on the internet. Although some overlap with existing rules may occur, I welcome any feedback or necessary adjustments. I plan to continue adding new rules to my repository as part of my ongoing research; however, I also want these rules to be available in the main Sigma repository to benefit the entire community and provide easier access when downloading Sigma rules from a centralized source.
This reverts commit ba843fb.
6b83e63
to
e8945a0
Compare
A couple of notes on rules that I removed/merged
|
Summary of the Pull Request
This PR introduces a set of Sigma rules originally published in my personal repository (https://github.com/tsale/Sigma_rules). The project was created to include unique rules based on my research, specifically targeting gaps in the open-source community. At the time of their creation, no similar rules were found in the main Sigma repository or elsewhere on the internet. Although some overlap with existing rules may occur, I welcome any feedback or necessary adjustments.
I plan to continue adding new rules to my repository as part of my ongoing research; however, I also want these rules to be available in the main Sigma repository to benefit the entire community and provide easier access when downloading Sigma rules from a centralized source.
Changelog
fix: Potential Privilege Escalation via Local Kerberos Relay over LDAP - Add new exclusion
fix: Sdiagnhost Calling Suspicious Child Process - Add new filters
new: Antivirus Filter Driver Disallowed On Dev Drive - Registry
new: ChromeLoader Malware Execution
new: Emotet Loader Execution Via .LNK File
new: Exploitation Attempt Of CVE-2020-1472 - Execution of ZeroLogon PoC
new: FakeUpdates/SocGholish Activity
new: File Explorer Folder Opened Using Explorer Folder Shortcut Via Shell
new: HackTool - SharpWSUS/WSUSpendu Execution
new: HackTool - SOAPHound Execution
new: Hiding User Account Via SpecialAccounts Registry Key - CommandLine
new: Injected Browser Process Spawning Rundll32 - GuLoader Activity
new: Kerberoasting Activity - Initial Query
new: Manual Execution of Script Inside of a Compressed File
new: Obfuscated PowerShell OneLiner Execution
new: OneNote.EXE Execution of Malicious Embedded Scripts
new: Potential CVE-2021-44228 Exploitation Attempt - VMware Horizon
new: Potential CVE-2022-22954 Exploitation Attempt - VMware Workspace ONE Access Remote Code Execution
new: Potential Defense Evasion Activity Via Emoji Usage In CommandLine - 1
new: Potential Defense Evasion Activity Via Emoji Usage In CommandLine - 2
new: Potential Defense Evasion Activity Via Emoji Usage In CommandLine - 3
new: Potential Defense Evasion Activity Via Emoji Usage In CommandLine - 4
new: Potential MOVEit Transfer CVE-2023-34362 Exploitation - Dynamic Compilation Via Csc.EXE
new: Python Function Execution Security Warning Disabled In Excel
new: Python Function Execution Security Warning Disabled In Excel - Registry
new: Raspberry Robin Initial Execution From External Drive
new: Raspberry Robin Subsequent Execution of Commands
new: Remote Access Tool - Action1 Arbitrary Code Execution and Remote Sessions
new: Remote Access Tool - Ammy Admin Agent Execution
new: Remote Access Tool - Cmd.EXE Execution via AnyViewer
new: Serpent Backdoor Payload Execution Via Scheduled Task
new: Uncommon Connection to Active Directory Web Services
new: Ursnif Redirection Of Discovery Commands
update: Potential CVE-2022-29072 Exploitation Attempt - Add additional shells and flags
Example Log Event
N/A
Fixed Issues
N/A
SigmaHQ Rule Creation Conventions