Introduction
The Miku Miku Beam server exposes both REST endpoints and real-time Socket.IO connections for managing network stress tests. The server is built with Echo framework and supports CORS for web client integration.Base Configuration
The server listens on the port configured in your settings (default: 8080).Authentication
Currently, the server does not require authentication. CORS is configured to allow requests from the origin specified in your configuration file.Available Endpoints
REST Endpoints
GET /attacks
List all available attack methods
GET /configuration
Retrieve current proxy and user agent configuration
POST /configuration
Update proxy and user agent configuration
Socket.IO Events
The server uses Socket.IO for real-time attack management and statistics.Client Events (Emit)
| Event | Description |
|---|---|
startAttack | Initiate a new stress test with specified parameters |
stopAttack | Stop the currently running attack |
disconnect | Disconnect from server (automatically stops attack) |
Server Events (Listen)
| Event | Description |
|---|---|
stats | Real-time statistics updates (packets/sec, total packets, logs) |
attackAccepted | Confirmation that attack has started |
attackError | Error message if attack cannot start |
attackEnd | Notification that attack has ended |
Attack Methods
The following attack methods are registered by default:http_flood- Standard HTTP flood attackhttp_bypass- HTTP flood with bypass techniqueshttp_slowloris- Slowloris connection exhaustion attacktcp_flood- Raw TCP packet floodminecraft_ping- Minecraft server ping flood
Proxy Support
The server supports proxy rotation for attacks. By default, proxies are required unless you:- Set
ALLOW_NO_PROXY=trueenvironment variable - Start server with
--no-proxyflag
Example: Basic Connection
Error Handling
HTTP Errors
REST endpoints return standard HTTP status codes:200 OK- Request successful400 Bad Request- Invalid request parameters500 Internal Server Error- Server error
Socket.IO Errors
Errors during attack execution are sent via theattackError event:
- No proxies available (when
ALLOW_NO_PROXYis false) - Invalid attack method
- Invalid target format
- Attack duration or size limits exceeded