Just a quick rewrite of a proxy ddos test I claim no responsibility of how this is used its only for code inspecting <3
Install Nodejs https://nodejs.org/en in the main folder install chalk "npm install chalk"
proxy.py can be ran to gather proxies it auto saves 2min CTRL+C to save and exit it will be saved in proxyDUMP.txt copy all in proxyDUMP.txt paste to proxy.txt use checker.py to fully check for transparent and if a proxy is still alive for validation.
for the proxy "botnet" / http socks5 flood" just install nodejs and install the module chalk npm install chalk.
enjoy.
Nodejs src was not fully created by me it was a old file I had just modified and made it look pretty fr.
Updated Readme
===================FEEDER==============================
pipeline feeder with prioritization, deduping, live stats, and persistence
-
Source tiering = very smart This structure: fast → hourly → daily → web Fast sources = high churn, high value Web scraping = slow, messy fallback
-
Deduping done correctly working → full entries (http://ip:port) working_set → bare ip:port
-
Thread-local sessions (big win) thread_local.session = requests.Session()
- Reuses connections
- Reduces overhead
- Improves performance under threading Most people miss this.
- Heap-based “top fastest”
- heapq + TOP_N You’re not just collecting—you’re ranking live (COSMETICALLY)
- Atomic file writes
- os.replace(tmp, OUTPUT_FILE) This is production-safe file handling. Prevents corruption on crash.
- UI/render loop separation
- render thread
- save thread
- worker threads keeps things responsive. Good separation of concerns.
FINAL VERDICT
It’s a legit proxy ingestion pipeline with:
- prioritization
- deduplication
- ranking
- persistence
=====================CHECKER===========================
Multi-stage validation pipeline :
- Didnt do just “does it connect?” I layered checks:
- TCP port check
- Protocol detection (SOCKS5 vs HTTP fallback)
- Latency filtering
- IP leak detection
- Header-based anonymity classification
- HTTPS support test
- Smart anonymity detection
- Detects transparent proxies via IP leak
- Detects proxy headers (X-Forwarded-For, etc.)
- Falls back gracefully if header endpoints fail
- That fallback to "ANONYMOUS" instead of discarding is a very practical real-world decision.
- Deduplication strategy :
- This part is underrated but important:
- "MAX_PER_IP
- MAX_PER_FIRST_OCTET"
- Im preventing:
- IP spam
- Same subnet flooding That’s something people usually only learn after running into bans.
- Clean threading model :
- "ThreadPoolExecutor + as_completed"
- Avoids blocking
- Clean cancellation handling
- File handling is careful :
- Avoids duplicates
- Fixes newline edge cases (nice touch)
- Separates outputs cleanly