Skip to main content

Overview

The mmb attack command launches network stress tests against a specified target using various attack methods. It provides real-time statistics and colored output for monitoring attack progress.

Syntax

Arguments

string
required
The attack method to use. Must be one of:
  • http_flood - Send random HTTP requests
  • http_bypass - Send HTTP requests that mimic real browser requests (redirects, cookies, headers, resources)
  • http_slowloris - Send slow HTTP requests and keep connections open
  • tcp_flood - Send random TCP packets
  • minecraft_ping - Send Minecraft ping/MOTD requests
string
required
The target URL or address to attack. Format depends on the attack method:
  • HTTP methods: http://example.com or https://example.com
  • TCP flood: http://example.com or tcp://host:port
  • Minecraft ping: minecraft.example.com:25565

Flags

integer
default:"60"
Duration of the attack in seconds. The attack will automatically stop after this time period.
integer
default:"500"
Delay between packets in milliseconds. Lower values increase attack intensity but may cause instability.
integer
default:"512"
Size of each packet in bytes. Larger packets consume more bandwidth per request.
integer
default:"0"
Number of concurrent threads to use. When set to 0 (default), uses the number of CPU cores available on the system.
boolean
default:"false"
Enable verbose mode to show detailed attack logs, including individual request attempts and proxy usage.
boolean
default:"false"
Allow running the attack without proxies. By default, the CLI requires proxies from data/proxies.txt. Use this flag to bypass that requirement.
Running attacks without proxies exposes your real IP address to the target server.
string
Path to a custom configuration file (TOML format). If not specified, uses default configuration.

Output

The command displays real-time statistics during the attack:

Output Fields

  • Timestamp - Current time in HH:MM:SS format
  • PPS - Packets per second (current rate)
  • Total - Total packets sent since attack started
  • Proxies - Number of proxies being used

Verbose Mode Output

With --verbose flag enabled, additional detailed logs are shown:

Examples

Attack Methods

HTTP Flood

Sends rapid random GET/POST HTTP requests to overwhelm the target server.
Best for: Basic HTTP stress testing, overwhelming server resources

HTTP Bypass

Mimics real browser behavior with realistic headers, cookies, and redirects to bypass basic protections.
Best for: Testing WAF/DDoS protection, realistic traffic simulation

HTTP Slowloris

Sends slow HTTP requests that keep connections open, exhausting server connection pools.
Best for: Connection exhaustion testing, low-bandwidth attacks

TCP Flood

Sends raw TCP packets with random data at the network layer.
Best for: Network layer stress testing, protocol resilience testing

Minecraft Ping

Sends Minecraft server status/ping requests to test game server resilience.
Best for: Minecraft server stress testing, MOTD request handling

Configuration

The CLI reads configuration from a TOML file (specified via --config or defaults). The configuration controls:
  • Proxies file location - Default: data/proxies.txt
  • User agents file location - Default: data/uas.txt

Proxy File Format

One proxy per line in data/proxies.txt:
Supported formats:
  • protocol://user:password@host:port - Full format with authentication
  • protocol://host:port - Without authentication
  • host:port - Uses HTTP as default protocol
  • host - Uses HTTP and port 8080 as defaults

User Agents File Format

One user agent string per line in data/uas.txt:

Stopping an Attack

Press Ctrl+C to gracefully stop a running attack:
The attack will stop immediately and clean up resources.

Error Handling

No Proxies Available

Solution: Either add proxies to data/proxies.txt or use --no-proxy flag.

Unsupported Attack Method

Solution: Check that the method name is correct and matches one of the supported methods.

Invalid Target Format

Solution: Ensure the target URL/address is in the correct format for the chosen attack method.

Performance Tips

Optimize thread count: Start with default (number of CPUs) and adjust based on system performance. More threads don’t always mean better performance.
Balance delay and intensity: Lower --delay values increase attack intensity but may overwhelm your network or system. Start with defaults and decrease gradually.
Use proxies effectively: More proxies distribute load better and reduce detection risk. Ensure proxy list is fresh and working.
High-intensity attacks (low delay, many threads, large packets) can consume significant system resources and bandwidth. Monitor system performance during attacks.
This tool is for educational purposes and authorized testing only. Only use against systems you own or have explicit written permission to test. Unauthorized stress testing is illegal in most jurisdictions.

See Also