~ GreeDoS a Cybersecurity Red Team tool based on DDoS ~
Description
-
Advanced Cybersecurity Red Team Tool
-
Test Network Resilience: Simulate multi-vector DDoS attacks to evaluate how well network defenses hold up under stress as penetration testing purpose.
-
Validate Security Controls: Assess the effectiveness of firewalls, intrusion prevention systems (IPS), and DDoS mitigation solutions in real-world scenarios.
-
Conduct Red Team Exercises: Use the tool during authorized penetration tests to mimic attacker behavior and identify weaknesses in infrastructure.
-
Improve Incident Response: Train SOC teams to detect, analyze, and respond to DDoS attacks by running controlled attack simulations.
-
Optimize Network Performance: Identify bottlenecks and failure points under high traffic loads, enabling proactive network tuning.
-
Automated Testing: Cybersecurity professionals can automate DDoS simulation tests within security testing suites, improving red teaming efficiency.
-
Rapid Deployment: Network engineers can deploy the tool across environments for stress testing network resilience without complex setup.
📫 How to reach me: http://mrechofi.github.io/Tanjib_portfolio_website/ & tanjibisham777@gmail.com & tanjibisham888@gmail.com
Installation Process via 'git' :
git clone https://github.com/MrEchoFi/GreeDoS_V2.git
cd GreeDoS_V2
// install external libraries,
pip install requests scapy rich
or,
pip install -r requirements.txt
// If you want to ensure everything is up-to-date, you can use:
pip install --upgrade requests scapy rich
// then run the tool,
python3 GreeDoS_ii.py
Note: Install Npcap externally.
Install Tcpreplay for high-speed packet replay:
sudo apt install tcpreplay
Recommendations:
- you can run this tool in Ubuntu, kali linux, WSL, Debian & Arch, Parrot OS.
- Use good level of router & ethernet cable.
- If u want to run this tool aggressively for testing or lab based attacks with more time & thread then use high CPU, GPU and RAM based device.
Metadata
Release files for greedos 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| greedos-0.4.0.tar.gz | 11.9 kB | Without provenance | Details for greedos-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| greedos-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for greedos-0.4.0-py3-none-any.whl |
Total release size: 23.6 kB
Release files / greedos-0.4.0.tar.gz
| Download URL | greedos-0.4.0.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c2a4d77127f83b1db2afab36c2fa8d1501b4524c6aa0c6b3687bf6a68abbe47
|
|
BLAKE2b-256 checksum How to use checksums |
db9e46bc62fcdcc5ffca3af0c5c25968e866efd9b288462c3635dd0971fed478
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / greedos-0.4.0-py3-none-any.whl
| Download URL | greedos-0.4.0-py3-none-any.whl |
|---|---|
| Size | 11.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a44c41b9de8b2e7663302869ff99bfbb22fb95d06dabaabec2bcf2cbf5f7a0f
|
|
BLAKE2b-256 checksum How to use checksums |
328d1378fcf6176ac40288905d7c5c6e8d3cca31f4f942b76cbc10f94db7a696
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for greedos 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.