Klyda

KO | EN

gitlite — search

#python #java #python3 #arduino #golang #machine-learning #rust #html #flask #javascript #seismology #nodejs

★ 51 Open GitHub ↗

Highly configurable script for dictionary/spray attacks against online web applications.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

The Klyda project has been created to aid in quick credential based attacks against online web applications. 
Klyda supports the use from simple password sprays, to large multithreaded dictionary attacks.

Klyda is a new project, and I am looking for any contributions. Any help is very appreciated. 
Klyda offers simple, easy to remember usage; however, still offers configurability for your needs:
- Mulithreaded tasks
- Combine wordlists for larger scale attacks
- Blacklisting data to narrow down results
- Limit thread speed for sneaky purposes

# Installation & Usage
**1)** Clone the Git repo to your machine, `git clone https://github.com/Xeonrx/Klyda` 
**2)** Cd into the Klyda directory, `cd Klyda` 
**3)** Install the neccessary modules via Pip, `pip install requests beautifulsoup4 colorama numpy` 
**4)** Display the Klyda help prompt for usage, `python3 klyda.py -h`

>Klyda has been mainly designed for Linux, but should work on any machine capable of running Python.

What Klyda needs to work are only four simple dependencies: URL to attack, username(s), password(s), and formdata.
## The URL
You can parse the URL via the ``--url`` tag. It should look something like this, `--url http://127.0.0.1` 
Remember to **never** launch an attack on a webpage, that you don't have proper permission to do so.
## Usernames
Usernames are the main target to these dictionary attacks. It could be a whole range of usernames, a few in specific, or perhaps just one.
That's all your decision when using the script. You can specify usernames in a few ways...

**1)** Specify them manually, `-u Admin User123 Guest` 
**2)** Give a file to use, or a few to combine, `-U users.txt extra.txt` 
**3)** Give both a file & manual entry, `-U users.txt -u Johnson924`
## Passwords
Passwords are the hard part to these attacks. You don't know them, hence why dictionary & brute force attacks exists. Like the usernames, you can
give from just one password, up to however many you want. You can specify passwords in a few ways...

**1)** Specify them manually, `-p password 1234 letmein` 
**2)** Give a file to use, or a few to combine, `-P passwords.txt extra.txt` 
**3)** Give both a file & manual entry, `-P passwords.txt -p redklyda24`
## FormData
FormData is how you form the request, so the target website can take it in, and process the given information. Usually you would need to specify a: username value, a password value, and sometimes an extra value. You can see the FormData your target uses by reviewing the network tab, of your browsers inspect element. For Klyda, you use the `-d` tag.

You need to use placeholders to Klyda knows where to inject in the username & password, when fowarding out its requests. It may look something like this...
`-d username:xuser password:xpass Login:Login`

`xuser` is the placeholder to inject the usernames, & `xpass` is the placeholder to inject the passwords. Make sure you know these, or Klyda won't be able to work.

Format the FormData as `(key):(value)`

## Blacklists
In order to Klyda to know if it hit a successful strike or not, you need to give it data to dig through. Klyda takes use of given blacklists from failed login attempts, so it can tell the difference between a failed or complete request. You can blacklist three different types of data...

**1)** Strings, `--bstr "Login failed"` 
**2)** Status Codes, `--bcde 404` 
**3)** Content Length, `--blen 11`

You can specify as much data for each blacklist as needed. If any of the given data is not found from the response, Klyda gives it a "strike", saying
it was a successful login attempt. Otherwise if data in the blacklists is found, Klyda marks it as an unsuccessful login attempt.
Since you give the data for Klyda to evaluate, false positives are non-apparent.

>If you don't give any data to blacklist, then every request will be marked as a strike from Klyda!

## Rate limiting & Threads
By default, Klyda only uses a single thread to run; but, you can specify more, using the `-t` tag. This can be helpful for speeding up your work.

However, credential attacks can be **very** loud on a network; hence, are detected easily. A targeted account could simply just receieve a simple lock due to too many
login attempts. This creates a DoS attack, but prevents you from gaining the users's credentials, which is the goal of Klyda.

So to make these attacks a little less loud, you can take use of the `--rate` tag. This allows you to limit your threads to a certain number of requests per minute. 
It will be formatted like this, `--rate (# of requests) (minutes)`

For example, `--rate 5 1` will only send out 5 requests for each minute. Remember, this is for each thread. If you had 2 threads, this would send 10 requests per minute.

## Example
Test Klyda out on the Damn Vulnerable Web App (DVWA), or Mutillidae.

`python3 klyda.py --url http://127.0.0.1/dvwa/login.php -u user guest admin -p 1234 password admin -d username:xuser password:xpass Login:Login --bstr "Login failed"`

`python3 klyda.py --url http://127.0.0.1/mutillidae/index.php?page=login.php -u root -P passwords.txt -d username:xuser password:xpass login-php-submit-button:Login --bstr "Authentication Error"`

## The Future
Like mentioned earlier, Klyda is still a work in progress. For the future, I plan on adding more functionality and reformating code for a cleaner look.

My top piority is to add proxy functionality, and am currently working on it.

Klyda

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README