Mirai - Daily Threat Report

Sunday, November 15, 2026

By Yazoul AI · automated

Daily Summary

Today’s Mirai activity shows 100 new samples, a 17% increase over the 7-day average of 86. The uptick is moderate and within normal daily variance, but the file type breakdown reveals a continued shift toward architecture-specific ELF binaries. No new C2 infrastructure was observed.

New Samples Detected

The sample set is dominated by .elf files (72), which is consistent with Mirai’s long-standing preference for stripped ELF payloads. The remaining samples are distributed across architecture-specific extensions: .x86, .arm, .arm5, .arm7, .i686, .mips, and .ppc each account for 2-3 samples. Notably, the presence of 3 .mpsl samples is worth monitoring. This extension has appeared in prior Mirai builds targeting embedded MIPS devices and could indicate an active build targeting routers and IoT gateways with older firmware. The .dbg samples (2) may be debug symbols or staging artifacts and warrant triage.

7-Day Trend

Today’s count of 100 versus the 86 average represents a moderate rise but falls short of a surge threshold. The 7-day window likely reflects normal fluctuation around a baseline, not a campaign-level escalation.

IOC Highlights

100 new IOCs were recorded, but with zero new C2 servers, these are likely payload hashes and file-level indicators rather than network infrastructure. SOC teams should prioritize matching these hashes against endpoint and email gateway telemetry rather than blocking new addresses.

Security Analysis

The absence of new C2 servers despite a rising sample count is the most analytically interesting signal today. In comparable Mirai campaigns, we typically see infrastructure provisioning track payload distribution proportionally. A rising payload count with flat C2 infrastructure suggests either reuse of existing command-and-control channels or distribution of dormant or staging binaries not yet configured with active C2. This pattern has been observed in prior Mirai build pipelines where operators batch-generate architecture-specific payloads ahead of a distribution push, then activate C2 afterward. Defenders should not interpret the lack of new infrastructure as reduced risk. Instead, retro-hunt existing Mirai IOCs against the 100 new hashes to identify overlap. As an immediate action, SOC teams should enable DNS and TLS fingerprinting on known Mirai C2 patterns and ingest the new hashes into EDR blocklists, treating today’s activity as possible pre-activation staging.

Further Reading

Data Sources

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

More Mirai Reports

Recent Malware Reports