Kimwolf Botnet Hijacks 2M Android Devices via Proxy Networks

Kimwolf Botnet Compromises Over 2 Million Android Devices for DDoS and Proxy Services

HIGH
January 6, 2026
5m read
MalwareCyberattackIoT Security

Impact Scope

People Affected

over 2 million

Industries Affected

TelecommunicationsMedia and Entertainment

Related Entities

Products & Tech

Android

Other

Kimwolf

Full Report

Executive Summary

A rapidly growing malware operation known as the Kimwolf botnet has compromised over two million devices globally. The botnet primarily targets low-cost Android-based TV boxes and streaming devices. Active since at least August 2025, the threat actors behind Kimwolf are monetizing their vast network of infected devices in several ways: launching large-scale Distributed Denial of Service (DDoS) attacks, forcibly installing applications onto the devices, and selling access to the devices as residential proxies. The botnet's unique propagation method involves leveraging commercial residential proxy networks to pivot and infect other vulnerable devices within local home networks, creating a self-perpetuating cycle of growth.

Threat Overview

The Kimwolf botnet represents a significant threat in the IoT landscape. Its focus on Android TV boxes and similar streaming devices allows it to amass a large number of 'always-on' endpoints with significant bandwidth, ideal for conducting powerful DDoS attacks. Researchers note that some past DDoS attacks, previously attributed to other botnets, may have actually been the work of Kimwolf.

The operators have established a multi-faceted business model:

  1. DDoS-for-Hire: The primary function, leveraging the combined bandwidth of 2 million devices to launch disruptive attacks.
  2. Proxy Service Sales: The infected devices are sold as residential proxies, allowing other malicious actors to route their traffic through legitimate home IP addresses to evade detection.
  3. Pay-Per-Install: The botnet is used to silently install unwanted applications on the infected devices, generating revenue for the operators.

The investigation also uncovered evidence of pre-infected TV boxes being sold, indicating a potential supply chain compromise or a close relationship between the malware operators and hardware distributors or proxy providers.

Technical Analysis

The botnet's success hinges on its ability to compromise devices behind NAT and firewalls. It achieves this by abusing legitimate residential proxy services. The attackers likely purchase access to a set of proxies, which are themselves compromised devices. From these initial footholds, they scan the local network segments (/24 subnets) for other vulnerable Android devices with open ports (e.g., ADB over TCP on port 5555) or default credentials.

Once a new device is compromised, it is infected with the Kimwolf malware, enrolled into the botnet, and can then be used to scan its own local network for more victims. This peer-to-peer-like propagation within local networks allows for exponential growth.

MITRE ATT&CK Techniques

Impact Assessment

The Kimwolf botnet has a multi-layered impact. The owners of the infected devices suffer from degraded performance, increased bandwidth consumption, and the risk of having their home IP address blacklisted for malicious activity. The victims of the DDoS attacks face service disruption and financial loss. The broader internet community is affected by the availability of a large, cheap residential proxy network that can be used to anonymize a wide range of cybercrime, from ad fraud to credential stuffing attacks. The scale of over 2 million devices makes Kimwolf a formidable tool in the hands of its operators.

Detection & Response

  • Network Monitoring: Home users and ISPs should monitor for unusual outbound traffic patterns from streaming devices, such as connections to known C2 servers or participation in SYN floods. Look for an unusual number of outbound connections on various ports.
  • Device Behavior: Monitor Android TV boxes for unauthorized application installations, unexplained sluggishness, or settings changes (like developer mode or ADB over TCP being enabled without user consent).
  • Endpoint Security: While less common for IoT devices, running a security scanner designed for Android can help detect the Kimwolf malware or other infections.

Mitigation

  • Secure Configuration: Users of Android TV boxes should immediately change default passwords and disable developer features like Android Debug Bridge (ADB) unless absolutely necessary. If ADB is needed, ensure it is password-protected and not exposed to the internet.
  • Network Segmentation: Isolate IoT devices like streaming boxes onto a separate network segment or VLAN. This can prevent a compromised TV box from being used to attack other more sensitive devices on the home network, such as laptops or NAS drives.
  • Firmware Updates: Regularly check for and apply firmware updates from the device manufacturer. This can patch vulnerabilities that botnets like Kimwolf exploit. This aligns with Software Update (D3-SU).
  • Purchase from Reputable Sources: Avoid purchasing low-cost, unbranded electronics from untrusted vendors, as they have a higher risk of being pre-infected with malware.

Timeline of Events

1
August 1, 2025
The Kimwolf botnet is reported to have been active since at least August 2025.
2
January 6, 2026
This article was published

MITRE ATT&CK Mitigations

Isolate IoT devices on a separate network segment to prevent them from attacking other devices on the network and to better monitor their traffic.

Mapped D3FEND Techniques:

Harden the configuration of Android devices by changing default passwords and disabling unnecessary services like ADB.

Mapped D3FEND Techniques:

Regularly apply firmware updates to patch vulnerabilities exploited by botnets.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

To defend against botnets like Kimwolf that target IoT devices, Platform Hardening is a critical first line of defense for end-users and manufacturers. For users of Android TV boxes, this means taking immediate steps to secure the device's configuration. This includes changing any default administrator passwords, disabling developer mode, and specifically ensuring that network-based debugging (ADB over TCP on port 5555) is turned off. These open ports are the primary entry point for this type of malware. Manufacturers have a responsibility to ship devices in a secure-by-default state, prompting users to create a unique password during setup and disabling all non-essential services. Hardening the platform by reducing its attack surface makes it significantly more difficult for automated scanners used by botnets to find and exploit vulnerable devices.

Given that Kimwolf propagates by scanning local networks from already-compromised devices, Network Isolation is a highly effective countermeasure in both home and corporate environments. All IoT devices, including smart TVs, streaming boxes, and cameras, should be placed on a separate Wi-Fi network or VLAN that is isolated from the primary network where sensitive devices like laptops and file servers reside. This guest network should have firewall rules that prevent devices on it from initiating connections to the primary network. This containment strategy ensures that even if a TV box becomes infected with Kimwolf, it cannot be used as a pivot point to attack more valuable assets on the same network. Furthermore, it allows for more targeted monitoring of traffic originating from the IoT segment, making it easier to spot the anomalous traffic patterns associated with botnet activity.

Sources & References

Kimwolf Android Botnet Grows Through Residential Proxy Networks
SecurityWeek (securityweek.com) January 5, 2026
Weekly Intelligence Report – 09 January 2026
CYFIRMA (cyfirma.com) January 8, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

BotnetKimwolfAndroidDDoSIoT SecurityResidential Proxy

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading