This readme is a bit outdated. You can read the blog post about ActiveAntiPhish for more info https://computeco.de/posts/2019-06-16_1.html
This repo takes advantage of a technique called database saturation. If your organization is successfully phished this tool allows the organization to increase the noise in the signal to noise ratio of the hacker's stolen credentials. This is done by providing the tool with a fake password list, fake username list, proxy list, the phishing page's callback url, and your organizations email domain extension.
It generates hundreds of fake username/password pairs that are injected into the phishing page.
The theory is that the phisher will abandon their database as validating thousands of fake accounts just to find the small amount of valid accounts is very annoying.
You can use the ActiveAntiPhish command line application by downloading the linux release or by installing the rust toolchain and installing aap with cargo install aap. You will then be able to run the aap program from the command line.
ActiveAntiPhish 0.4.1 GNU-GPL-3.0
Saturate the bad guys' databases.
USAGE:
aap [FLAGS] [OPTIONS] --time <run_time> --threads <threads> --url <url>
FLAGS:
-g, --debug Locks application to one thread and displays HTTP response data.
-r, --getparams The form uses GET parameterized data.
-h, --help Prints help information
-i, --noredir Ignore redirects.
-m, --multipart The form uses multipart data.
-w, --urlencoded The form uses www-urlencoded data.
-V, --version Prints version information
OPTIONS:
-c, --ccn <ccn_field> The form field where a credit card number should be populated.
-k, --cookie <cookie>... Provide a cookie name and data <name=data>.
-s, --custom <custom>... Provide a custom field name and data <name:data>.
-v, --cvv <cvv_field> The form field where a credit card verification value should be populated.
-d, --domain <domain> The domain of the email server associated with your organization (otherwise random
domains will be used). For example: example.com or mail.example.com
-e, --email <email_field> The form field where an email should be populated.
-x, --exp <exp_field> The form field where a credit card expiration date should be populated.
-f, --fname <fname_field> The form field where a first name should be populated.
-l, --lname <lname_field> The form field where a last name should be populated.
-p, --pass <password_field> The form field where an password should be populated.
-L, --list <password_list> Locks application to one thread and displays HTTP response data.
-o, --phone <phone_field> The form field where an phone number should be populated.
-t, --time <run_time> Number of seconds until program exits.
-S, --social <ssn_field> The form field where a US social security number should be populated.
-n, --threads <threads> Number of threads to use. Default: 20
-u, --url <url> The path to the endpoint to POST fake data to.
This project maintains a collection of active and inactive phish kits that are unredacted. They are encrypted to protect from leechers and to protect the identities of hackers. Please contact me to be vetted for the decryption password.
In the rules directory you can find a yara ruleset for the phishkits in this repo as well as a generic rule for detecting phishing page source code (phish kits all use a similar design/coding style).
You can find current phishing advisories in ADVISORIES.md.