k4yt3x/orbitaldump

A simple multi-threaded distributed SSH brute-forcing tool written in Python

orbitaldump's Issues

Connection error

python orbitaldump.py -t 28 -u "D:\Stuff\ssh brute\usernames.txt" -p "D:\Stuff\ssh brute\pass2.txt" -h ###.##.###.90 --port 22 --proxies

Gives a huge number of connection errors with any number of threads.

unicodeDecodeError

'utf-8' codec can't decode byte 0xf1 in position 933: invalid continuation byte

False positive failover

Without a failover to prevent false positives, you will get completely unreliable results due to SonicWall etc.
Easiest approach:
stdin, stdout, stderr = ssh.exec_command("/sbin/ifconfig") output = stdout.read() if 'inet' in output etc...

BTW: This is not "distributed" credential stuffing, as this would be based on multiple hosts communicating targets/credentials with each other and "distribute" the workload (usually following a p2p majority voting approach).

If you use ThreadPool etc., why no CIDR-range for hosts or at least a hosts file? Makes the proxy approach quite timid.
The same can btw. be achieved by using proxychains and any random related tool.

Loop in jobs queue.

The actual situation: After all jobs queue tested (no valid credential found), program would repeat all jobs queue again automatically.
What's the reason for that?