Serving Random Payloads with Apache mod_rewrite
A tutorial on how to use Apache mod_rewrite to randomly serve payloads in phishing attacks
Serving Random Payloads with Apache mod_rewrite
A tutorial on how to use Apache mod_rewrite to randomly serve payloads in phishing attacks
Serving Random Payloads with Apache mod_rewrite Description
As testers, we sometimes need some good, old-fashioned trial and error to get things working. Phishing is one of the attacks that commonly takes more than one attempt to get payloads and command and control (C2) working properly. This post covers how to help effectively perform payload trial and error by randomly serving payloads from one URL with Apache mod_rewrite. The technique described in this post lends itself more to a penetration test, where email phishing batches may span an entire target company, rather than a red team assessment, where email phishing is highly targeted and payload issues are painstakingly troubleshot manually. Following the steps below, we can configure an Apache redirector, or server directly, to serve a random payload from a predefined list of possible payloads with the RewriteMap - randomized plain text functionality of Apache. Apache’s RewriteMap function allows external programs, such as scripts, databases, or text files to remap requests for Apache to serve. The example commonly used in the official documentation is if a store changes from a URL structure of item-1234 to iPhone-7-white, the web administrators could use Apache to serve up iPhone-7-white when item-1234 is requested without having to change any hard coded links.
Serving Random Payloads with Apache mod_rewrite FAQ
Common questions about Serving Random Payloads with Apache mod_rewrite including features, pricing, alternatives, and user reviews.
Serving Random Payloads with Apache mod_rewrite is A tutorial on how to use Apache mod_rewrite to randomly serve payloads in phishing attacks. It is a Security Operations solution designed to help security teams with C2, Payload Generation.
