Tuesday, March 4, 2025
HomeBotnetHajime Worm wrestle with Mirai Botnet to Control of your IoT Devices

Hajime Worm wrestle with Mirai Botnet to Control of your IoT Devices

Published on

SIEM as a Service

Follow Us on Google News

[jpshare] Hajime Worm First Discovered on  October  2016 and it used to spreads via unsecured devices with self-replication module that have open Telnet ports and use default passwords.

Hajime Worm Battle with Mirai Botnet indicate that ,Hajime was specifically created to protect against Mirai .

According to Symantec  ,Unlike Mirai, which uses hardcoded addresses for its command and control (C&C) server, Hajime is built on a peer-to-peer network.

“There isn’t a single C&C server address, instead the controller pushes command modules to the peer network and the message propagates to all the peers over time”

After contacts  C&C server address , it returns a cryptographically-signed message every ten minutes. The message, which is displayed on the device’s terminal .

Just a white hat, securing some systems.
Important messages will be signed like this!
Hajime Author.
Contact CLOSED
Stay sharp!

The malware’s Author didn’t include a DDoS highlight, didn’t utilize his botnet to malicious traffic activity, or some other nosy operation.

Hajime is also stealthier and more advanced in comparison to Mirai. Once on an infected device, it takes multiple steps to conceal its running processes and hide its files on the file system.

Hajime Replicating  Quickly:

According to the Symantec  Tracking Report, past Few month it spreading very fast and Target the DVRs, CCTV systems, and other poorly-protected Internet of Things (IoT) devices.

                                           Image Credits: Symantec

Symantec Researcher ,Waylon Grange said, ,once Hajime infects a device it blocks access to ports 23, 7547, 5555, and 5358, which are all ports that have been exploited in the past by IoT malware.

Once Hajime Hide its file in infected systems,The author can open a shell script to any infected machine in the network at any time, and the code is modular, so new capabilities can be added .

Doesn’t have (DDoS) capabilities :

Reason Behind of the worm, it does not have any distributed denial of service capabilities .

For the past six months, Hajime has been using its self-replication module to fight with Mirai and other IoT botnet for control over IoT devices.

Hajime is an enemy of  Mirai Botnet:

Hajime was specifically created to protect against Mirai ,All pieces of information indicate the conclusion that Hajime was made to specifically attack Mirai, and  reduce the number of devices Mirai can infect.

Hajime Act as White Hat and powerful than Mirai .These white worms is that they usually turn out to have a short lifespan.

Symantec Said ,”To have a lasting effect, the firmware would need to be updated. It is extremely difficult to update the firmware on a large scale because the process is unique to each device and in some cases is not possible without physical access.”

Also Read:

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 Exploiting AES Encryption for Stealthy Payload Protection

Cybersecurity researchers have uncovered a surge in the use of Advanced Encryption Standard (AES)...

33.3 Million Cyber Attacks Targeted Mobile Devices in 2024 as Threats Surge

Kaspersky's latest report on mobile malware evolution in 2024 reveals a significant increase in...

Routers Under Attack as Scanning Attacks on IoT and Networks Surge to Record Highs

In a concerning trend, the frequency of scanning attacks targeting Internet of Things (IoT)...

Google Launches Shielded Email to Keep Your Address Hidden from Apps

Google is rolling out a new privacy-focused feature called Shielded Email, designed to prevent apps...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

BADBOX Botnet Surges: Over 190,000 Android Devices Infected, Including LED TVs

The BADBOX botnet, a sophisticated malware operation targeting Android-based devices, has now infected over...

Phorpiex Botnet Distributes LockBit Ransomware Through Compromised Websites

Cybereason Security Services has published a comprehensive threat analysis highlighting the resurgence of the...

Murdoc Botnet Exploiting AVTECH Cameras & Huawei Routers to Gain Complete Control

Researchers have identified an active malware campaign involving a Mirai botnet variant, dubbed Murdoc,...