Skip to content
July 20, 2026
  • Linkedin
  • Twitter
  • Facebook
  • Youtube

Daily CyberSecurity

Zero-hour alerts. Unmatched analysis.

Primary Menu
  • Home
  • CVE Data
    • CVE Watchtower
    • Top Exploited CVEs
    • CVE Stats by Vendor
    • Q2 2026 Report
  • Cyber Criminals
  • Data Leak
  • Linux
  • Malware
  • Vulnerability
  • Submit Press Release
  • Weekly Recap
Light/Dark Button
  • Home
  • News
  • Malware
  • New Satori botnet used Huawei zero-day & 280,000 IP addresses was infected in 12 hours
  • Malware

New Satori botnet used Huawei zero-day & 280,000 IP addresses was infected in 12 hours

Do Son December 24, 2017 7 minutes read
Satori botnet
Add Daily CyberSecurity as a preferred source on Google

The Mirai botnet, which had caused the Great Eastern Breaking Network in the United States, took a bad look, followed by much larger botnets monitored by security researchers than Mirai’s “zombie army.” Li Fengpei, the security researcher at 360 Institute of Cyber Security, once released a series of in-depth monitoring reports on Mirai and contributed to the subsequent fall of Mirai. Recently, a great deal of attention was drawn to the “Satori” Botnet.

Satori has infected more than 280,000 IP addresses in as little as 12 hours, controlling hundreds of thousands of home routers with the newly discovered zero-day vulnerabilities more quickly than Mirai – and by comparing Mirai’s power to A gun, then Satori is a cannon. However, this “cannon” is currently on the same scale as a time bomb, but it has not yet started its course.

Image source: bleepingcomputer

Satori is even more horrible than Mirai

Satori was initially tracked on behalf of Mirai Okiru and showed a trail around November 23. Many security companies claim Satori’s vast majority of “broilers” are located in Argentina. Since then, the botnet began to wreak havoc in Egypt, Turkey, Ukraine, Venezuela, and Peru.

360 Institute for Cybersecurity, Fortinet, and Check Point released research findings on Satori on their respective blogs on December 5, December 12 and December 21 (Note: 360 Institute for Cybersecurity is still in November Released on the 24th a related security warning “early warning of security threats: new Mirai botnet variant is actively spreading on ports 23 and 2323”).

In a blog post on December 5, “Security Threat Warning: Mirai Variant Satori is Similar to Worms on Ports 37215 and 52869,” 360 Institute for Cyber Security said: “In our previous blog, we mentioned about 10 Thousands of independent scanning IPs from Argentina are scanning ports 2323 and 23 and are confirming that this is a new variant of Mirai In the past few days scanning has become more severe and more countries have appeared on our ScanMon platform After careful analysis we saw more of the part, realizing that the previous 2323/23 port scan was just a small part of the huge puzzle. “

It can be said that Satori is essentially similar to a worm and its source code is derived from Mirai and is an upgrade of Mirai, but Satori is much more “poisonous” than Mirai.

  1. After infected with IoT devices, Mirai will further try to find the vulnerable device by telnet scanning and use the Mirai Trojan program to infect. Instead of using the scanner component, Satori utilizes two embedded vulnerabilities to Infects remote devices connected to ports 37215 and 52869. This means that Satori approximates the Internet of Things worm and spreads itself without the need for additional components.
  2. Mirai looks for vulnerable devices by scanning ports 2323 and 23, Satori is a device that connects to ports 37215 and 52869 and has either of the two known vulnerabilities, but does not fix it.

Frighteningly, one of the vulnerabilities was later certified as 0day (now available for fixes).

Satori is directed at the Huawei router

Li Fengpei told Lei Feng network, after everyone concerned about the point in the camera, in fact, the router has now exceeded the camera, became the “first broiler.”

Checkpoint and Fortinet were directly named, saying that this Satori is running a Huawei router. Moreover, the above 0day exists in a Huawei router.

Lei Fengwang noticed that Huawei released a security announcement on November 30, “There is a remote code execution vulnerability in the HG532 product.” (Updated on December 22), acknowledging the existence of a Huawei security router vulnerability, And made recommendations for restoration.

On November 27, 2017, Huawei received a notice from Check Point Software Technology Research Division that there was a remote code execution security vulnerability (CVE-2017-17215) for the Huawei HG532 product. Meanwhile, Check Point issues security alert CPAI-2017-1016, but the alert does not include the vulnerability details. Huawei launched the first survey analysis. It has been confirmed that the loophole exists. The authenticated attacker can send malicious packets to the port of device 37215 to attack and successfully exploit the vulnerability to execute arbitrary code remotely.

The following measures can be taken to circumvent or prevent this vulnerability. For more information, contact your local service provider or Huawei TAC.

1) Configure the device’s built-in firewall function

(2) modify the default password

(3) operator-side deployment of the firewall

Customers can deploy Huawei NGFW or data center firewall products and upgrade the IPS signature database to the latest version released on December 1, 2017 (IPS_H20011000_2017120100) to detect and protect this vulnerability from the network layer.

Huawei has always followed the industry practice of life cycle management and has established a life cycle management system that specifies the product life cycle strategy and product termination strategy. For non-full stop service Huawei has communicated with the customer and provided a solution according to the customer’s suggestion. Huawei has discontinued the service. Huawei recommends that users avoid or prevent this problem by using evasion measures or replace the service with a newer model.

Relevant investigations are ongoing, and Huawei PSIRT will update the security bulletin. Please pay close attention to the security bulletin for this vulnerability.

According to a Zhongguancun Online report, the Satori-controlled routers are provided to customers by two of the largest carriers, allowing operators to quickly locate and fix device vulnerabilities.

According to Bleeping Computer, many botnets and cybersecurity companies intervened in the past week and won C & C servers for the Satori botnet. After these servers were taken, the number of botnets vanished from 500,000 to 700,000 units.

But the other did not give up resistance. After the server was captured, 52869 and 37215 port scanning activity showed a huge peak. Most likely, Satori’s authors are thinking of trying to scan ports and look for broilers.

 

Source: Bleepingcomputer, Source: 360 Institute of Cyber Security

In a November 29 CheckPoint article, Check Point researchers revealed the identity of the author of the Satori botnet, Nexus Zeta.

The researchers said they have tracked down to him because the domain name used by the author to sign up for Satori’s infrastructure has an e-mail address that is highly associated with an account with HackForums, one of the most popular hacking forums.

Check Point said: “Although he was not very active in such a forum, he was at a loss.”

The day before the Satori event was discovered, November 22, a forum post showed that Nexus Zeta was asking for help to create a Mirai botnet (Editor’s Knockout Blackboard: Satori is a variant of Mirai).

 

However, according to Bleeping Computer, Satori has not been identified as having been associated with any major source of DDoS attacks over the past few weeks.

Li Fengpei believes that Bleeping Computer’s point of view is limited to “recent + major attacks”, which is consistent with what they have observed. However, the situation may not be the same if we trace it forward.

The aforementioned blog post of 360 Institute for Cyber Security pointed out: “We also suspect this attack is related to another IoT IoT-related attack that took place in China in August 2017. Perhaps we will release another blog elaboration later. ”

Even more frightening is that Satori’s story is far from over, and we have to worry about other botnets and attacks.

Li Fengpei on Lei Feng said that as Mirai’s source code has been open on the Internet, the transformation of Mirai, in its variant form of identity, the construction of a huge botnet has long been difficult. Moreover, the attacker can find a new domain name is completely replaced, the identity is very secretive.

Reference: bleepingcomputer

Related coverage

  • Spy vs. Spy: Predator Malware Now Hunts the Researchers
  • Eternidade Stealer: New Python WhatsApp Worm Uses IMAP Email for Covert C2 and Brazilian Bank Overlays
  • XCSSET macOS Malware Evolves: New Variant Targets Firefox, Hijacks Clipboard for Crypto Theft
  • Game Over: “RenEngine” Malware Hides in Pirated Visual Novels
  • Rhysida Ransomware Threat Grows: FBI and CISA Warn
Track all actively exploited CVEs →

Support Our Threat Intelligence

If you find our CVE report and cybersecurity news helpful, consider supporting our work.

Buy Me a Coffee Logo Buy Me a Coffee PayPal
Crypto QR Code
USDT (TRC20):
TN8BdV8cp4T1Cd28gK9qTAnZknzzuwyUtm
USDT (ERC20):
0x3725e1a7d3bc5765499fa6aaafe307fabcd75bce

Share this article:

Facebook Post LinkedIn Telegram
Written by
@DdoS · Security Researcher

Do Son

Do Son is the Founder and Editor of SecurityOnline.info. Working in cybersecurity since 2013, he reports on vulnerabilities, malware, and emerging threats, providing timely analysis to help organizations and individuals stay ahead of evolving risks.

Tags: Satori botnet

Search

Translation

CVE WATCHTOWER
🚨

Receive alerts for vulnerabilities being exploited in the wild.

⚡

Get notified instantly when a Proof of Concept (PoC) exploit is published.

🔍

Access critical info on vulnerabilities even when marked as "RESERVED".

🧠

Insights powered by decades of expertise and global intelligence sources.

🎯

Customize alerts with up to 10 keywords for your specific tech stack.

📊

Export the raw CVE database for SIEM integration and reporting.

Upgrade Package

🚨 Active Exploits in the Wild

  • CVE-2026-6875CVSS 9.5
    ServiceNow has addressed a remote code execution vulnerability that was identified in the ServiceNow AI platform. This vulnerability...
    Admin intel📅 Updated: Jul 18, 2026
  • CVE-2026-39808CVSS 9.8
    A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox...
    CISA KEV📅 Added to KEV: Jul 16, 2026
  • CVE-2026-25089CVSS 9.8
    A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiSandbox...
    CISA KEV📅 Added to KEV: Jul 16, 2026
  • CVE-2026-58644CVSS 9.8
    Deserialization of untrusted data in Microsoft Office SharePoint allows an unauthorized attacker to execute code over a network.
    CISA KEV📅 Added to KEV: Jul 16, 2026
  • CVE-2023-4346CVSS 7.5
    KNX devices that use KNX Connection Authorization and support Option 1 are, depending on the implementation, vulnerable to...
    CISA KEV📅 Added to KEV: Jul 15, 2026
  • CVE-2026-53362
    In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation...
    Admin intel📅 Updated: Jul 14, 2026
  • CVE-2026-46242CVSS 7.8
    In the Linux kernel, the following vulnerability has been resolved: eventpoll: fix ep_remove struct eventpoll / struct file...
    Admin intel📅 Updated: Jul 14, 2026
  • CVE-2026-56155CVSS 7.8
    Insufficient granularity of access control in Active Directory Federation Services (AD FS) allows an authorized attacker to elevate...
    CISA KEV📅 Added to KEV: Jul 14, 2026
Powered by CVE Watchtower

🔴 Live Critical Threats

  • CVE-2026-12701CVSS 9.0
    A path traversal vulnerability was found in pulpcore. The relative_path_validator function only...
  • CVE-2026-64620CVSS 9.8
    FreeRDP before 3.28.0 (affected
  • CVE-2026-16242CVSS 9.4
    A flaw was found in the Konnectivity proxy-server configuration for hosted control...
  • CVE-2026-16235CVSS 9.8
    Crypt::Password versions through 0.28 for Perl generate insecure random values for salts....
  • CVE-2026-13147CVSS 9.1
    The Kirki WordPress plugin before 6.0.12 does not validate a user-supplied URL...
  • CVE-2026-44359CVSS 10.0
    Meshtastic is an open source mesh networking solution. Prior to version 2.7.21.1370b23,...
  • CVE-2026-64162CVSS 9.8
    In the Linux kernel, the following vulnerability has been resolved: idpf: fix...
  • CVE-2026-64160CVSS 9.8
    In the Linux kernel, the following vulnerability has been resolved: netfs: Fix...
  • CVE-2026-64150CVSS 9.8
    In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_inner:...
  • CVE-2026-64142CVSS 9.8
    In the Linux kernel, the following vulnerability has been resolved: ksmbd: close...
Powered by CVE WATCHTOWER

Our Websites
  • Penetration Testing Tools
  • The Daily Information Technology
  • Top Exploited CVEs
  • Daily CyberSecurity

    • About SecurityOnline.info
    • Advertise with us
    • Announcement
    • Contact
    • Contributor Register
    • Login
    • Disclaimer
    • DCMA
    • Privacy Policy
    • About SecurityOnline.info
    • Advertise on SecurityOnline.info
    • Contact Us

    When you purchase through links on our site, we may earn an affiliate commission. Here’s how it works

    • CVE Watchtower
    • CVE Statistics by Vendor 2026
    • Q2 2026 Report
    • Top Exploited CVEs
    • Linkedin
    • Twitter
    • Facebook
    • Youtube
    © 2017 - 2026 Daily CyberSecurity. All Rights Reserved.