feat(rules): New Suspicious file delivery via HTML smuggling rule#595
Open
rabbitstack wants to merge 1 commit intomasterfrom
Open
feat(rules): New Suspicious file delivery via HTML smuggling rule#595rabbitstack wants to merge 1 commit intomasterfrom
Suspicious file delivery via HTML smuggling rule#595rabbitstack wants to merge 1 commit intomasterfrom
Conversation
Detects suspicious file delivery via HTML smuggling, a phishing technique where malicious payloads are embedded inside HTML files and reconstructed on the victim system using browser-side JavaScript. Adversaries abuse spearphishing attachments for initial access while bypassing traditional email and network-based security controls.
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.
What is the purpose of this PR / why it is needed?
Detects suspicious file delivery via HTML smuggling, a phishing technique where malicious payloads are embedded inside HTML files and reconstructed on the victim system using browser-side JavaScript. Adversaries abuse spearphishing attachments for initial access while bypassing traditional email and network-based security controls.
What type of change does this PR introduce?
/kind feature (non-breaking change which adds functionality)
Any specific area of the project related to this PR?
/area rules
Special notes for the reviewer
Does this PR introduce a user-facing change?