Python-Node.js Fusion Framework with 30+ attack vectors, 15+ bypass techniques, and professional security testing capabilities.
READ CAREFULLY BEFORE USE
This framework is designed EXCLUSIVELY for:
- β Legal Penetration Testing (with written authorization)
- β Security Research (in authorized environments)
- β Authorized Stress Testing (own infrastructure only)
STRICTLY PROHIBITED:
- β Unauthorized system access
- β Attacks without explicit permission
- β Any illegal activities
- β Script kiddie behavior
YOU ARE SOLELY RESPONSIBLE for your actions. Unauthorized use is illegal and punishable by law under:
- Computer Fraud and Abuse Act (USA)
- Computer Misuse Act (UK)
- EU Cybersecurity Directives
- Your local jurisdiction laws
# Clone repository
git clone https://github.com/petangZi/dripcorn.git
cd dripcorn
# Install dependencies
npm run setup
# Or manual installation:
npm install
pip install -r requirements.txt --break-system-packages# Start framework
npm start
# Or directly
node index.jsOn first run, you'll be prompted to:
- Scan QR code with authenticator app
- Enter 6-digit verification code
- Save your secret key securely
- π HTTP Flood (GET/POST/PUT)
- π Slowloris (Connection Exhaustion)
- π’ Slow POST (R.U.D.Y)
- π Slow Read
- π₯ Cache Buster
- πͺ Cookie Bomb
- π Redirect Loop
- π― SYN Flood (requires root)
- π‘ UDP Flood
- β ACK Flood
- π RST Flood
- π ICMP Flood
- β‘ HTTP/2 Rapid Reset (CVE-2023-44487)
- π WebSocket Flood
- π‘ Server-Sent Events
- π£ XML Bomb (Billion Laughs)
- π₯ JSON Bomb
- #οΈβ£ Hash Collision
- π ReDoS (Regex DoS)
- π₯ CPU Exhaustion
- π SSL Renegotiation
- π SSL Exhaustion
- π‘οΈ TLS Flood
- π IP Rotation
- π Proxy Chain (HTTP/SOCKS5)
- π User-Agent Rotation
- π Header Randomization
- π TLS Fingerprint Spoofing
- β° Timing Randomization
- π Browser Emulation
- πͺ Cookie Management
- βοΈ CloudFlare Bypass
- π‘οΈ WAF Evasion
# Launch framework
npm start
# Select: Attack Vectors > Layer 7 > HTTP Flood
# Enter target: http://localhost:3000
# Configure: duration=30, rps=100
# Confirm disclaimers and launch# Requires sudo privileges
sudo npm start
# Select: Attack Vectors > Layer 4 > SYN Flood
# Enter target: 192.168.1.100
# Port: 80
# Packets/sec: 1000
# Duration: 30npm start
# Select: Bypass Techniques > Proxy Rotation
# Framework will test all proxies
# Shows working vs failed proxies- Startup Disclaimer - Legal terms before framework access
- Pre-Attack Disclaimer - Authorization confirmation before each attack
- Audit Logging - All actions logged with timestamps
- TOTP-based two-factor authentication
- Required before framework access
- QR code setup with authenticator apps
- Encrypted secret storage
All actions logged to: ~/.dripcorn/logs/audit.log
Log includes:
- Timestamp
- User information
- System details
- Attack parameters
- Target information
Create .env file:
# Proxy Configuration
HTTP_PROXY=http://proxy.example.com:8080
SOCKS_PROXY=socks5://proxy.example.com:1080
# 2Captcha API (for CAPTCHA bypass)
CAPTCHA_API_KEY=your_api_key_here
# Monitoring
MONITOR_PORT=8080Create proxies.txt:
http://proxy1.example.com:8080
http://proxy2.example.com:8080
socks5://proxy3.example.com:1080
View attack statistics:
- Total attacks launched
- Success/failure rates
- Attack duration and metrics
- Target information
- Timestamp logs
Access via: Main Menu > Statistics
# Install Python 3.9+
# macOS
brew install python3
# Ubuntu/Debian
sudo apt install python3 python3-pip
# Windows
# Download from python.org# SYN Flood requires root
sudo python3 attacks/syn_flood.py <args>
# Or run framework with sudo
sudo npm start# Clean install
rm -rf node_modules package-lock.json
npm install
# Python deps
pip install -r requirements.txt --break-system-packagesScenario: Testing client web application security
1. Obtain written authorization
2. Launch DripCorn V2
3. Test various attack vectors
4. Document vulnerabilities
5. Generate report for client
Scenario: Researching new DoS mitigation techniques
1. Set up isolated lab environment
2. Deploy test infrastructure
3. Launch controlled attacks
4. Measure mitigation effectiveness
5. Publish findings
Scenario: Testing own infrastructure resilience
1. Deploy target on own servers
2. Configure monitoring
3. Launch graduated attacks
4. Identify bottlenecks
5. Implement improvements
Full documentation available in docs/ directory:
ATTACKS.md- Detailed attack vector documentationBYPASS.md- Bypass technique guidesAPI.md- Framework API referenceLEGAL.md- Legal compliance guide
dripcorn-v2/
βββ index.js # Main framework
βββ package.json # Node dependencies
βββ requirements.txt # Python dependencies
βββ attacks/
β βββ syn_flood.py # SYN flood script
β βββ dns_amp.py # DNS amplification
βββ docs/ # Documentation
βββ logs/ # Audit logs
Contributions welcome! Please:
- Fork repository
- Create feature branch
- Commit changes
- Push to branch
- Open pull request
MIT License - see LICENSE file
Developed by RedOps Security Lab
Special thanks to the security research community.
- Issues: GitHub Issues
- Docs:
/docsdirectory - Email: security@redops.lab
Found a vulnerability? Please report responsibly:
- Do NOT publicly disclose
- Email: security@redops.lab
- Include detailed POC
- Allow time for patch
We appreciate responsible security researchers.
Remember: Stay legal. Stay ethical. Stay safe. π¦β¨