crypto_campaign #3240
Open
crypto_campaign #3240
Conversation
This file contains 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
nasbench
requested changes
Dec 17, 2024
detections/endpoint/windows_account_access_removal_via_quser_logoff.yml
Outdated
Show resolved
Hide resolved
detections/endpoint/windows_obfuscated_files_or_information_via_rar_sfx.yml
Outdated
Show resolved
Hide resolved
detections/endpoint/windows_obfuscated_files_or_information_via_rar_sfx.yml
Outdated
Show resolved
Hide resolved
detections/endpoint/windows_obfuscated_files_or_information_via_rar_sfx.yml
Show resolved
Hide resolved
detections/endpoint/windows_obfuscated_files_or_information_via_rar_sfx.yml
Show resolved
Hide resolved
nasbench
requested changes
Jan 7, 2025
detections/endpoint/windows_account_access_removal_via_powershell_initiate_logoff.yml
Outdated
Show resolved
Hide resolved
detections/endpoint/windows_bidirectional_communication_via_telegram_bot.yml
Outdated
Show resolved
Hide resolved
detections/endpoint/windows_bidirectional_communication_via_telegram_bot.yml
Outdated
Show resolved
Hide resolved
Comment on lines
12
to
17
| search: '`sysmon` EventCode=22 query = "api.telegram.org" | ||
| | stats count min(_time) as firstTime max(_time) as lastTime by query answer QueryResults QueryStatus process_name process_guid Computer | ||
| | rename Computer as dest | ||
| | `security_content_ctime(firstTime)` | ||
| | `security_content_ctime(lastTime)` | ||
| | `windows_bidirectional_communication_via_telegram_bot_filter`' |
There was a problem hiding this comment.
To be confirmed but I believe The logic needs to exclude the telegram binary on windows because it communicates with the API itself.
I don't know if there is a direct link from the web but excluding browsers is will also avoid FPs
| description: The following analytic detects instances where file or folder permissions are modified to grant read-only access. Such changes are characterized by the presence of read-related permissions (e.g., R, REA, RA, RD) and the absence of write (W) or execute (E) permissions. Monitoring these events is crucial for tracking access control changes that could be intentional for restricting access or indicative of malicious behavior. Alerts generated by this detection help ensure that legitimate security measures are enforced while unauthorized changes are promptly investigated. | ||
| kind: endpoint | ||
| search: '| tstats `security_content_summariesonly` min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Processes | ||
| where Processes.process_name IN( "icacls.exe", "cacls.exe", "xcacls.exe") AND Processes.process IN ("*/grant*", "*/G*") AND Processes.process IN ("*SYSTEM*", "*admin*", "*S-1-1-0*", "*EVERYONE*") |
There was a problem hiding this comment.
Is there a specific reason we only focus on these groups for read only? I think any file being set to read only is interesting.
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.
New Detection
updated
tagged
story
What does this PR have in it? Screenshots are worth 1000 words 😄
Checklist
<platform>_<mitre att&ck technique>_<short description>nomenclatureNotes For Submitters and Reviewers
buildCI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.