Tuesday, December 3, 2024
HomeBackdoorOutlaw Hacking Group Using Command Injection Flow To Attack Organizations Network using...

Outlaw Hacking Group Using Command Injection Flow To Attack Organizations Network using Botnet via C&C Server

Published on

SIEM as a Service

Outlaw Hacking group uses command injection vulnerability in IoT devices and Linux servers to distribute botnets. The threat actors compromised the FTP servers of Japanese institution and Bangladeshi government site.

Security researchers from TrendMicro uncovered the hacking operation named “Outlaw”, the hacker group used compromised servers and linked to availability cluster to host an IRC bouncer, which was used to command and control the emerging botnet.

Along with exploiting files, the attackers used hacking tools to target organizations through DoS and SSH brute force. Researchers caught the operation by placing a number of honeypots and capturing injected commands.

- Advertisement - SIEM as a Service

The botnet used is a shell botnet variant written in Perl and the script is available in Github and the same botnet was distributed before in shellshock vulnerability.

The payload used is the n3 file that runs with Perl interpreter, once the both installed on the system it continuously communicates with the C&C server if in case the internet is disconnected it will reconnect again.

Once the shellbot executed on the server the administrator of IRC can send continuous commands to perform ort scan, perform various forms of distributed denial of service (DDoS), download a file, get information about other machines, or just send the operating system (OS) information and list of certain running processes on the C&C server.

The botnet continuously scans for the following ports

“All infected hosts also showed base C&C connection in the form of PING/PONG traffic, occasionally asked for updates, and provided some host information like suspicious crontab-like records and the process identifier (PID) of the sd-pam process of the user who was running the IRC bot on the system.”

Also, researchers spotted several identities such as Luci, Lucian, Dragos, mazy, hydra, and poseidon were spotted in IRC communication channels.

“The Outlaw group here used an IRC bot, which isn’t a novel threat. The code used is available online, making it possible to build such a bot and operate it under the radar of common network security solutions.”

Read More:

Chalubo Botnet Compromise Your Server or IoT Device & Use it for DDOS Attack

Torii Botnet – A New Sophisticated IoT Botnet Attack in Wide – More Powerful Than Mirai

Hackers Offering DDoS-for-Hire Service Powered by Bushido Botnet in Dark Web Markets

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Threat Actors Allegedly Claims Breach of EazyDiner Reservation Platform

Reports have emerged of a potential data breach involving EazyDiner, a leading restaurant reservation...

Salesforce Applications Vulnerability Could Allow Full Account Takeover

A critical vulnerability has been discovered in Salesforce applications that could potentially allow a...

TP-Link HomeShield Function Vulnerability Let Attackers Inject Malicious Commands

A significant vulnerability has been identified in TP-Link's HomeShield function, affecting a range of...

ElizaRAT Exploits Google, Telegram, & Slack Services For C2 Communications

APT36, a Pakistani cyber-espionage group, has recently upgraded its arsenal with ElizaRAT, a sophisticated...

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

Threat Actors Allegedly Claims Breach of EazyDiner Reservation Platform

Reports have emerged of a potential data breach involving EazyDiner, a leading restaurant reservation...

Salesforce Applications Vulnerability Could Allow Full Account Takeover

A critical vulnerability has been discovered in Salesforce applications that could potentially allow a...

TP-Link HomeShield Function Vulnerability Let Attackers Inject Malicious Commands

A significant vulnerability has been identified in TP-Link's HomeShield function, affecting a range of...