LWescott create body_encrypted_zip_password_attachment.yml #3488
Conversation
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
github-actions
bot
added
the
in-test-rules
Member
Author
|
Telemetry is catching all relevant behavior... marking r4r |
aidenmitchell
approved these changes
Nov 24, 2025
IndiaAce
deleted the
luke_create_encrypted_attachment_with_password_in_body
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
From a runner. There's an opportunity here to create some detection-in-depth by creating a rule for emails with an attached zip that contain language suggesting "the password for the encrypted file is: ___" sales invoked ADE and put a new rule in their env, and we have the encrypted attachment detection as well but again, the more the merrier.
Associated samples
Associated hunts