sammwyy/mikumikubeam

An open-source network stresser tool but it's Hatsune Miku

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 54 minutes ago
Added to GitGenius on September 11th, 2026
Created on January 20th, 2025
Open Issues & Pull Requests: 71 (+0)
GitHub issues: Enabled
Number of forks: 534
Total Stargazers: 5,850 (+0)
Total Subscribers: 37 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.1 hours
Mean response time: 9.6 days
90th percentile: 24.3 days
Tracked items: 83

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 12% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 64
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 485 days
Stale 30+ days: 63
Stale 90+ days: 60

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Miku Miku Beam is a network stresser tool with a Hatsune Miku-themed interface built in Go.

The tool addresses the need for stress testing servers by providing a visually engaging platform that combines attack functionality with real-time visualization. It implements multiple attack methods including HTTP flood, HTTP bypass with header and cookie mimicry, HTTP Slowloris, TCP flood, and Minecraft ping attacks. The architecture separates concerns into a CLI component for terminal-based operation, a core engine handling attack coordination and method implementations, a web server with Socket.IO for real-time communication, and a React-based frontend featuring the Miku theme. Attacks run using multi-threaded goroutines for performance, and the tool supports simultaneous attacks from multiple clients with isolated instances per client.

Developers should adopt this tool if they need a stress testing solution with both command-line and web-based interfaces. The project suits scenarios where real-time attack visualization and live statistics tracking are valuable, and where the themed interface appeals to users. The tool distinguishes itself through its configurable attack parameters accessible via frontend controls, support for proxy rotation, and the ability to run attacks from either CLI with colored output or through a web interface with Socket.IO-driven live updates.

Almost all open issues are raised by outside users rather than the core team, indicating a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a day.