January 23, 2017 By Larry Loeb 2 min read

The Ragebot botnet malware first hit the cybersecurity scene in the middle of 2015. Instead of pinging servers with HTTP requests per the standard method, this malware notably used Internet Relay Chat (IRC) to converse with bots under its control.

This process may have been an attempt to avoid detection. While novel, it was a rather inefficient way to run the attack. But it appears that the malware creators have learned from their past mistakes.

The Return of Ragebot Botnet Malware

According to Bleeping Computer, Ragebot is back with some nasty new attributes. The latest version targets only Windows machines because they contain the communication mechanism the malware now uses in most of its installations.

The malware opens a File Transfer Protocol (FTP) connection to a remote server and then downloads a payload that does the real heavy lifting. First, the payload acts as a scanner looking for any internal subnetworks or hosts that allow communication over port 5900, which facilitates virtual network computing (VNC) remote desktop connections in Windows.

Ragebot then attempts a brute-force login with the 296 passwords it has on a list. If it gains entry, it infects the machine.

More Nasty New Features

Ragebot still uses IRC for the command-and-control (C&C) server operation after it infects — that much hasn’t changed. The new version does, however, seem specially redesigned to keep cybersecurity researchers from identifying it.

For example, Ragebot now features a protection system that keeps the malware running by blocking all other processes and permitting only the whitelisted core system applications to run. The malware authors hope this function will keep hunter-killer programs at bay.

The new version also looks for local RAR files to infiltrate as part of what appears to be a secondary self-propagation system. When stuck inside the RAR file, the malware will look like a normal process and attract no attention.

While the new version doesn’t eliminate the bandwidth limitations of using IRC as a side-channel communication method, the resurgence of Ragebot points to the need to be aware of existing threats. There is always someone out there looking to compromise unsuspecting users’ data.

More from

We are moving!

< 1 min read - SecurityIntelligence.com is being sunset, but have no fear!We have a new home for all of your favorite security and X-Force content.Follow us to www.ibm.com/think to maintain access to the stories and news you love, both new and old.Security Intelligence will officially sunset on Friday, March 28, 2025. To access the latest security thought leadership, go here. To access the latest X-Force research, go here.If you are experiencing cybersecurity issues or an incident, contact X-Force® to help:US hotline: 1-888-241-9812 | Global hotline:…

Bypassing Windows Defender Application Control with Loki C2

10 min read - Windows Defender Application Control (WDAC) is a security solution that restricts execution to trusted software. Since it is classified as a security boundary, Microsoft offers bug bounty payouts for qualifying bypasses, making it an active and competitive field of research.Typical outcomes of a WDAC bypass bug bounty submission:Bypass is fixed; possible bounty awardedBypass is not fixed but instead "mitigated" by being added to the WDAC recommended block list. Likely no bounty awarded but honorable mention is typically givenBypass is not…

FYSA — VMware Critical Vulnerabilities Patched

< 1 min read - SummaryBroadcom has released a security bulletin, VMSA-2025-0004, addressing and remediating three vulnerabilities that, if exploited, could lead to system compromise. Products affected include vCenter Server, vRealize Operations Manager, and vCloud Director.Threat TopographyThreat Type: Critical VulnerabilitiesIndustry: VirtualizationGeolocation: GlobalOverviewX-Force Incident Command is monitoring activity surrounding Broadcom’s Security Bulletin (VMSA-2025-0004) for three potentially critical vulnerabilities in VMware products. These vulnerabilities, identified as CVE-2025-22224, CVE-2025-22225, and CVE-2025-22226, have reportedly been exploited in attacks. X-Force has not been able to validate those claims. The vulnerabilities…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today