Saturday, December 21, 2024
HomeDDOSMirai Based Botnet Moobot Exploit Hikvision Vulnerability

Mirai Based Botnet Moobot Exploit Hikvision Vulnerability

Published on

SIEM as a Service

Fortinet has recently discovered a malware called Moobot, which was widely distributed through a security vulnerability in a number of Hikvision surveillance or security cameras. Moobot is a variant of the well-known botnet malware Mirai. 

When a victim device is infected, it turns the device into a member of its botnet army, accepts instructions from the threat actors, and launches Distributed Denial of Service (DDoS) attacks against specific targets.

Infection Process

Moobot exploited a vulnerability CVE-2021-36260 in the webserver of Hikvision’s various surveillance cameras to invade. 

- Advertisement - SIEM as a Service

A specially crafted message of malicious commands sent to Hikvision devices with this vulnerability, that can yield this vulnerability and inject malicious code for infection.

According to the Fortinet report, The method of attacking Hikvision products is very simple, and it does not even need to pass any login verification procedures, as long as a special attack message is sent to the target device to succeed.

After Moobot got infected, it modify some common commands, such as the “reboot” command used to restart the device, so that the administrator cannot restart the hacked device.

Apart from this, the Moobot features several common elements of Satori, it’s also a variant of Mirai botnet, and in the summer of 2020, the author of Satori got arrested.

Here are the similarities of Moobot with Satori:-

  • Using a separate downloader.
  • The forking of the “/usr/sbin*” process.
  • Overwriting the legitimate “macHelper” file with the Moobot executable.

Floods used

Incorporating the compromised device into a DDoS swarm is the primary goal of Moobot, and in this proceeding to attack the C2 sends several floods with the target IP address and port number.

Here are the floods used by Moobot:-

  • UDP flood
  • ACK flood
  • ACK+PUSH flood
  • SYN flood

However, the vulnerability CVE-2021-36260 has been already fixed in the new version of Hikvision’s firmware launched in September 2021.

But, here, most IoT product owners will hardly update the product, in short, there are still a large number of unpatched products that will be there on the market, which will make it a perfect target for hackers.

While the experts recommended users frequently check whether the products they own have the security updates available or not. Also make sure that the products are updated with the latest version, to avoid becoming the targets of attackers and tools utilized by the hackers to launch attacks.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates.

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Threat Actors Selling Nunu Stealer On Hacker Forums

A new malware variant called Nunu Stealer is making headlines after being advertised on underground hacker...

Siemens UMC Vulnerability Allows Arbitrary Remote Code Execution

A critical vulnerability has been identified in Siemens' User Management Component (UMC), which could...

Foxit PDF Editor Vulnerabilities Allows Remote Code Execution

Foxit Software has issued critical security updates for its widely used PDF solutions, Foxit...

Windows 11 Privilege Escalation Vulnerability Lets Attackers Execute Code to Gain Access

Microsoft has swiftly addressed a critical security vulnerability affecting Windows 11 (version 23H2), which...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Over 300,000 Prometheus Servers Vulnerable to DoS Attacks Due to RepoJacking Exploit

The research identified vulnerabilities in Prometheus, including information disclosure from exposed servers, DoS risks...

Europol Shutsdown 27 DDoS Service Provider Platforms

In a major international operation codenamed “PowerOFF,” Europol, collaborating with law enforcement agencies across...

Hackers Exploit Docker Remote API Servers To Inject Gafgyt Malware

Attackers are exploiting publicly exposed Docker Remote API servers to deploy Gafgyt malware by...