Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT/Embedded Security //

Botnet

11/7/2018
08:05 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

'Outlaw' IRC Bot Roughs Up Windows & Open Source Environments

Trend Micro is having a showdown with a IRC bot developed by a group dubbed 'Outlaw,' which is targeting Windows, Ubuntu and even Android environments.

A new Internet Relay Channel (IRC) bot, which is built with the help of the Perl language-based Shellbot, is targeting Windows-based environments, along with Ubuntu Linux and even Android devices, according to a blog post from the Trend Micro Cyber Safety Solutions Team.

The researchers stuck the name of "Outlaw" on the group behind this bot. The name is a translation from Romanian word for the tool -- haiduc -- that the threat actors use.

The group has spread the bot through the use of a common command injection vulnerability on Internet of Things (IoT) devices, as well as Linux servers. Trend reports that the IRC channel used for control of the bot had 142 infected hosts as members.

While Trend's honeypots found the existence of the bot, they also found that the Outlaw group had compromised an File Transfer Protocol (FTP) server of a Japanese art institution, along with a Bangladeshi government site. The Bangladeshi attack took advantage of a vulnerability on a Dovecot mail server.

The botnet itself, which has been available on GitHub, had previously been spread through the Shellshock vulnerability. Trend's research found that it is now spreading through previously brute-forced or compromised hosts.

Once installed, the bot is in resident. The connection to the control IRC channel occurs immediately after infection and is persistent. If connectivity is lost, the bot will immediately reconnect once an Internet connection returns.

The administrator of the IRC channel can send commands to the backdoor-infected host. Trend discovered that the possibilities included commands to perform a port scan, launching distributed denial of service (DDoS) attacks, downloading a file, getting information about other machines on the network, sending the operating system information, as well as a list of certain running processes that are present on the command-and-control (C&C) server.

DDoS-related activity affects User Data Protocol (UDP), TCP and HTTP traffic, according to Trend.

Researchers also found that the infected IRC hosts showed base C&C connection in the form of PING/PONG traffic. The IRC needs this sort of challenge and response to keep the connection open. In addition, the IRC bot occasionally asks for updates, as well as providing some host information.

That information might include suspicious crontab-like records, along with the process identifier (PID) of the sd-pam process of the user who was running the IRC bot on the system.

Using an IRC bot isn't a novel threat, but it may be able to sneak in under the radar of many security measures. Trend suggests enterprise should mitigate the threat by setting up the SSH login process properly, which means not leaving it open to public networks unless it is necessary for your infrastructure.

Monitoring non-DNS traffic coming to and from port 53 is also highly recommended.

Restricting the use of FTP as much as possible is also desirable. This is the method that is usually used for loading the exploit files to the victim systems.

Measures like these will help to prevent outlaws from roping and stealing your cattle.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.