Skip to main content
Mallory
← Back to News
botnet-infrastructureembedded-device-vulnerabilityrapid-weaponizationdefault-credential-exposure

Mirai Variants Exploit Newly Disclosed IoT and Network Device RCE Flaws

Malware Intelligence · 5 sources · Updated 3mo ago · First seen Mar 15, 2021

Mirai Variants Exploit Newly Disclosed IoT and Network Device RCE Flaws

Mirai-related botnets remained highly active as operators rapidly incorporated newly disclosed remote code execution flaws and weak-credential attacks against internet-facing IoT and network security devices. Palo Alto Networks Unit 42 reported an active campaign exploiting vulnerabilities including CVE-2021-27561, CVE-2021-27562, CVE-2021-22502, and CVE-2020-26919 across products such as SonicWall SSL-VPN, D-Link DNS-320, Yealink Device Management, Micro Focus Operation Bridge Reporter, Netis routers, and Netgear ProSAFE Plus devices. Fortinet likewise observed roughly 200 attacks per day in a three-week honeypot study, with nearly 4,000 of about 4,700 Telnet attacks tied to Mirai-related malware families and variants quickly adding exploits such as OptiLink GPON RCE, CVE-2021-1498, and CVE-2021-31755.

Successful compromises typically fetched shell scripts that installed multi-architecture Mirai binaries, and in some cases added SSH brute-force and scanning tools, attempted persistence, removed artifacts, and blocked management ports to retain control. Researchers said the broader botnet ecosystem also remained resilient beyond Mirai alone: Fortinet identified active variants including SORA, SYLVEON, Hajime, and MANGA, while earlier Netlab 360 analysis showed Hajime continuing to grow through a modular peer-to-peer architecture and propagation via TR-069 flaws and weak Telnet credentials. The combined reporting underscores that unpatched edge devices and default or weak passwords continued to fuel large-scale botnet expansion.

Hunt this familyPull IOCs and campaign context straight into your stack.
Get the IOCs
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

17 events · 2016 – Apr 10, 2023
  1. Apr 10, 20234y ago

    Unit 42 observes IZ1H9 Mirai campaign targeting Linux and networking devices

    Unit 42 reported observing the Mirai variant IZ1H9 exploiting exposed Linux-based servers and networking devices on 2023-04-10. The report says the campaign had been active since November 2021 and used brute-forced SSH/Telnet credentials plus HTTP-accessible RCE flaws including CVE-2023-27076, CVE-2023-26801, and CVE-2023-26802.

    Old Wine in the New Bottle: Mirai Variant Targets Multiple IoT Devices
  2. Reported Jun 24, 20215y ago

    FortiGuard sees MANGA add new exploit vectors

    FortiGuard Labs reports that the MANGA Mirai variant recently added exploits for OptiLink ONT1GEW GPON RCE, CVE-2021-1498, and CVE-2021-31755. The report also says MANGA targeted a broader set of vulnerabilities including CVE-2021-22986, CVE-2020-25506, CVE-2021-22502, CVE-2021-27561, CVE-2021-27562, and SonicWall VisualDoor.

    The Ghosts of Mirai | FortiGuard Labs
  3. Reported Jun 24, 20215y ago

    FortiGuard observes active Mirai variants including SORA and SYLVEON

    FortiGuard Labs identifies SORA and SYLVEON among the Mirai variants actively observed in its honeypot data. It also notes recently updated SYLVEON binaries on a download server, indicating the variant was still being actively operated.

    The Ghosts of Mirai | FortiGuard Labs
  4. Reported Jun 24, 20215y ago

    FortiGuard honeypot records sustained Mirai-family activity

    FortiGuard Labs reports that over a three-week observation period its telnet honeypot received nearly 4,700 connections and about 200 attacks per day on average, with nearly 4,000 attacks attributed to Mirai-related malware families. The data showed Mirai-derived botnets remained highly active.

    The Ghosts of Mirai | FortiGuard Labs
  5. Mar 15, 20216y ago

    Unit 42 reports Mirai campaign still active

    Unit 42 says the attacks were still ongoing when the report was published on March 15, 2021. The campaign was actively exploiting vulnerabilities in devices from vendors including SonicWall, D-Link, Yealink, Micro Focus, Netis, and Netgear.

    Mirai Variant Targeting New IoT Vulnerabilities, Network Security Devices
  6. Mar 13, 20216y ago

    Mirai samples add Netgear ProSAFE Plus exploit

    Unit 42 states that an exploit for CVE-2020-26919 was added to the malware samples on 2021-03-13. This further broadened the campaign's targeting of exposed devices.

    Mirai Variant Targeting New IoT Vulnerabilities, Network Security Devices
  7. Mar 3, 20216y ago

    Mirai samples add Micro Focus OBR exploit

    Unit 42 reports that on 2021-03-03 the same malware samples were served from a third IP address with an added exploit for CVE-2021-22502. This showed the campaign rapidly expanding its exploit set.

    Mirai Variant Targeting New IoT Vulnerabilities, Network Security Devices
  8. Feb 23, 20216y ago

    Mirai infrastructure updated to serve Yealink exploits

    Unit 42 says one IP involved in the campaign was updated on 2021-02-23 to serve a Mirai variant leveraging CVE-2021-27561 and CVE-2021-27562. The report notes these Yealink exploits were incorporated within hours of public disclosure.

    Mirai Variant Targeting New IoT Vulnerabilities, Network Security Devices
  9. Feb 16, 20216y ago

    Unit 42 first observes Mirai campaign targeting IoT and security devices

    Unit 42 reports that it first observed the Mirai-based campaign on 2021-02-16. The activity targeted internet-facing network security and IoT devices through multiple remote code execution vulnerabilities.

    Mirai Variant Targeting New IoT Vulnerabilities, Network Security Devices
  10. Aug 29, 20179y ago

    Researchers capture Hajime config referencing x64 support

    Netlab 360 says it captured a signed Hajime configuration file on 2017-08-29 that contained settings for x64 CPU support. The finding suggested either planned expansion beyond IoT architectures or possible signing-key compromise, with researchers favoring expansion.

    Is Hajime botnet dead?
  11. Aug 18, 20179y ago

    Additional Hajime updates observed in August and September 2017

    Netlab 360 reports further Hajime updates on 2017-08-18, 2017-08-19, 2017-08-22, and 2017-09-04. The report characterizes these as patches to existing code rather than dramatic changes.

    Is Hajime botnet dead?
  12. Aug 12, 20179y ago

    Hajime update on August 12 correlates with bot growth

    Netlab 360 identifies another Hajime update on 2017-08-12. Researchers linked this update with a rapid increase in active Hajime nodes.

    Is Hajime botnet dead?
  13. Aug 6, 20179y ago

    Hajime update on August 6 correlates with bot growth

    Netlab 360 reports a Hajime update on 2017-08-06 and says bot numbers increased quickly after this and a later August update. The event reflects active maintenance of the botnet.

    Is Hajime botnet dead?
  14. Aug 2017

    Hajime file updates resume in August 2017

    Netlab 360 says Hajime file updates resumed in August 2017 after the July lull. The renewed updates were associated with a quick increase in active bot numbers.

    Is Hajime botnet dead?
  15. Jul 2017

    Hajime activity declines in late July 2017

    Netlab 360 reports that Hajime activity declined in the second half of July 2017 and that no botnet file updates occurred during that period. This lull preceded a renewed wave of updates and growth.

    Is Hajime botnet dead?
  16. Oct 2016

    Rapidity Networks discovers the Hajime botnet

    Netlab 360 states that Rapidity Networks first discovered the Hajime botnet in October 2016. This marks the earliest referenced public identification of Hajime in the provided sources.

    Is Hajime botnet dead?
  17. 2016

    Mirai source code is publicly released

    FortiGuard Labs notes that Mirai source code was publicly released in late 2016, enabling many copycat IoT botnet variants to emerge. This release helped drive the later proliferation of Mirai-derived malware families.

    The Ghosts of Mirai | FortiGuard Labs
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Malware

1 linked

Affected products

4 linked
Device ManagementDns-320Ssl VpnOperations Bridge Reporter

Organizations

6 linked
D-LinkNetgearSonicwallNetis SystemsMicro Focus International plcYealink Network Technology Co., Ltd.

Observables

217 linked

Indicator values are masked on this page. View all 217 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
Hunt This Malware
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.