New Feature: Set Custom User-Agent for Phishlets #1115
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
DrorDvash
changed the title
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.
A
custom_uafield has been added to each phishlet in the configuration. Allows users to specify a custom User-Agent, which will be injected into the HTTP request before sending it to the server.Some websites deliver different content depending on the User-Agent, and manipulating the User-Agent can help bypass certain security measures.
Usage:
Simply update the
custom_uafield like so:phishlets custom_ua <phishlet> "<ua>"Log output:
NOTE: When a "new visitor has arrived" it will print the original User-Agent but will send to the server the custom one.
Also, Thanks to @An0nUD4Y for his solution, which inspired this addition.