This software is a replica of one of the most iconic and used tools of offensive security: proxychains
Essentially, this is a TCP + UDP proxychains implementation
Over the years, I would not have been able to carry out several activities without proxychains. However, there were times when I would have found certain features useful — features that the original author has not yet introduced
The code is certainly a mess BUT it gets the job done!
I also want to take this opportunity to thank the entire community of pentesters, red teamers, and hackers. Your studies, research, articles, posts, blogs, tools, and videos have helped me grow. This software is a tribute to all of you in the cybersecurity world, I hope you find it useful!:D
If you want to clone it, credit me in the readme.md.
- UDP support by --udp flag ( both ipv4 - ipv6 )
- SOCKS proxy selection by -id flag
Feel free to share what others features may be useful!
Before you ask me, proxychains's references are intentional(:
Compiling and POC:
snmp.mp4
The configuration file is always proxychains.conf, but you can choose what socks proxy you want to use to forward your traffic, just adding an ID as prefix. For example:
mem.mp4
- GLIBC_2.38
git clone https://github.com/NULLhere/Proxando.git
cd Proxando
make clean && CFLAGS="-DDEBUG" ./configure && make ----> to enable logs
make clean && ./configure && make ----> to disable logs
The limitations are the same of the original one: this program works only on dynamically linked programs, so what cannot be intercepted is:
- binaries statically compiled
- direct syscalls ( mount, ntpdate, etc etc.. )
I'm not planning to add support for those anytime soon, but I would love to in the future!
I'm just busy with other things at the moment. I believe the most viable way to intercept direct syscalls would be through ptrace(), but that would require a looooot of work - so stay tuned!
This software is intended for legitimate use only, such as authorized penetration testing and/or nonprofit educational purposes. It should only be used on networks that you own or have explicit written permission from the owner to test.
Misuse of this software for illegal activities, including unauthorized network intrusion, hacking, or any activity that violates applicable laws, is strictly prohibited. The author assumes no responsibility or liability for any damage, misuse, or legal consequences arising from the use of this software. By using airgeddon, you agree to indemnify and hold harmless the project contributors from any claims or legal action.
It is the user's sole responsibility to ensure compliance with all applicable local, state, national, and international laws. If you are unsure about your legal rights to use this software, you should consult with an attorney before proceeding.
This software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, or non-infringement. In no event shall the author or copyright holder be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the software or the use or other dealings in the software.
Use this software at your own risk.
If you find any issues, please report them in as much detail as possible so I can try to reproduce them in my environment! Include things like: the software involved, Wireshark traffic captures, the proxy you are using, the scenario, and anything else that might help
As I mentioned earlier, I don't know when (or if) I will be able to fix them, so feel free to open a pull request with a fix, I will review it as soon as I can!(: