New Trigger Technique #29
Merged
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
added 4 commits
May 3, 2017 14:32
…a rule to autodelete the form message as it hits the inbox. Which triggers the embedded payload
…to delete innocent emails
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.
Adds @monoxgas technique for triggering the form payload. Thanks Nick!
He found that setting the VBScript payload and not assigning any event handlers, would cause the VBScript to execute on delete.
Ruler now has
form add --rulewhich will create an auto delete rule. The rule will use a random trigger word. If you don't send the trigger email, you'll need to send an email with the specified trigger word before the form will trigger.This form does not have
openreplyforwardtriggers.To trigger using this method, append the
--ruleflag