How shubhushubhu99/ravan works
Project type and purpose
• From the file tree (two scripts: Ravan2.sh and Ravan3.py) and the README, this is an open‑source command‑line tool for launching phone‑number DDoS (OTP/call bombing) attacks.
• It’s not a full‑stack web app or microservice platform, but a small CLI utility that orchestrates HTTP requests (optionally through Tor) to third‑party SMS/call gateway APIs.
File structure
• Top‑level files:
• LICENSE
• README.md
• Ravan2.sh (Bash wrapper, now marked “API DEAD”)
• Ravan3.py (Python implementation, “WORKING”)
• No subdirectories; no database, UI, or backend server layers.
• Configuration and dependencies are implicit in the scripts (e.g., Tor, Python requests library).
README for additional insights
• Purpose: unlimited OTP bombing; optional Tor proxy.
• Dependencies: Tor (for Ravan2.sh), Python runtime (for Ravan3.py).
• Features: attack orchestration, proxy support, stop calling/messaging.
a. Main components
• User’s Terminal (CLI)
• Ravan2.sh Bash script (deprecated) / Ravan3.py Python script (current)
• Tor network (optional proxy layer)
• External SMS/Call Gateway APIs (e.g., public OTP endpoints)
• Target Phone Number Endpoint
b. Relationships and interactions
1. User invokes Ravan3.py with a target phone number.
2. Script composes HTTP requests to one or more SMS/call gateway endpoints.
3. If Tor mode is enabled, the script routes HTTP traffic through Tor’s SOCKS proxy.
4. Gateway APIs send OTPs or automated calls to the target phone.
c. Architectural patterns and principles
• Single‑process CLI tool (no concurrency beyond Python threads or async if implemented).
• External integration pattern: treat SMS/Call gateways as third‑party services.
d. Key technologies
• Bash (Ravan2.sh)
• Python 3 (Ravan3.py)
• requests (or similar HTTP library)
• Tor (SOCKS proxy)
• Public SMS/call provider APIs
Detailed elements to capture
• Input parser (phone number + options)
• Request dispatcher (iterates through providers)
• Proxy manager (handles Tor socket)
• Environmental dependencies: annotate that Tor must be running on localhost:9050.
• Error handling path (e.g., fall back to direct call if Tor not available).
Final advice
• Don’t over‑engineer—this is a linear CLI orchestration tool, so a simple left‑to‑right flow is ideal.
• Every distinct piece (user, script logic, proxy, third‑party API, phone network).