jgamblin/mirai-source-code

Leaked Mirai Source Code for Research/IoC Development Purposes

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 3 minutes ago
Added to GitGenius on September 7th, 2026
Created on October 2nd, 2016
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 3,526
Total Stargazers: 9,479 (+0)
Total Subscribers: 549 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Mirai Source Code is a repository containing the leaked source code of a botnet malware designed for research and indicator-of-compromise development purposes.

The repository holds the complete Mirai botnet codebase, which historically infected IoT devices through default or weak credentials and coordinated them to launch distributed denial-of-service attacks. The source includes the bot component that runs on compromised devices, the command-and-control server that directs them, a loader that performs telnet-based brute-force infection, and supporting scripts for building and deployment. The code is written primarily in C and requires a Linux build environment with cross-compilation tools to target multiple IoT architectures including MIPS and ARM.

This material is intended exclusively for cybersecurity researchers, malware analysts, and security professionals developing detection capabilities in isolated laboratory environments. The repository explicitly warns against any use targeting real devices or networks and emphasizes the need for complete network isolation when studying the code. Researchers should use virtual machines with host-only or internal networking to prevent accidental exposure. The original leak documentation is included to provide historical context and technical background.

The project maintains the leaked source as a static archive for reference and analysis rather than as an actively developed tool. The repository includes the original forum post and licensing information from the leak itself, along with structured documentation of the codebase components and their functions.