Mirai - Daily Threat Report

Sunday, June 28, 2026

Daily Summary

Mirai sample collection rose to 100 new submissions on June 28, marking a 17% increase over the 7-day average of 86. The volume is trending upward, driven by a surge in standard ELF payloads, though no new C2 infrastructure was observed today.

New Samples Detected

Today’s 100 samples were dominated by 70 .elf binaries, a notable concentration that accounts for 70% of the total. The remaining samples include 7 shell scripts (.sh), likely used for initial download and execution stages, and a scattering of architecture-specific builds: .ppc (3), .x86 (3), .mipsel (2), .x86_64 (2), .m68k (2), .arm8 (2), .mips (2), and .arm (2). The broad architectural spread suggests automated cross-compilation is active, with no single non-ELF format representing a breakout. The presence of .sh files may indicate a shift toward multi-stage infection chains that use scripts to fetch ELF payloads post-compromise, rather than embedding everything in a single binary.

IOC Highlights

While no new C2 servers were registered, the 100 samples contributed 100 new IOCs. These IOCs should be immediately ingested into SIEM and network monitoring tools. Given the absence of fresh C2 infrastructure, many of these IOCs likely point to intermediary download URLs or staging servers. SOC analysts should prioritize inspecting any outbound connections from internal hosts to IPs associated with these IOCs, especially if they involve HTTP or wget activity targeting newly observed .sh or .elf downloads.

Security Analysis

Today’s spike in standard .elf samples paired with zero new C2 domains suggests either a re-use of existing C2 infrastructure or a deliberate shift to decentralized command models. The historical Mirai pattern of launching new botnet clusters typically correlates with fresh C2 rollouts, so the current anomaly may indicate threat actors are recycling or hiding their control servers behind fast-flux or P2P mechanisms. Defenders should harden SSH and Telnet administrative interfaces on IoT devices, as these remain the primary initial access vectors for Mirai, and ensure any unused remote services are disabled or firewalled off immediately.

Further Reading

Data Sources

MalwareBazaar (abuse.ch) ThreatFox (abuse.ch) URLhaus (abuse.ch)

More Mirai Reports

Recent Malware Reports