BADBOX 3.0: Android TV boxes and AOSP devices — 40B daily ad-fraud bid requests, residential proxy enrollment
Severity: high · Patch status: partial · Since 2026-11-21
HUMAN Security's Satori team published research on BADBOX 3.0, a rebuilt version of the BADBOX Android botnet that returned after the 2025 takedowns. HUMAN says it generated roughly 40 billion fraudulent ad bid requests a day at its height, more than 4% of the CTV traffic its platform observed and more than three times the volume of the previous record holder, VASTFLUX. The malware infects cheap phones, tablets and streaming TV boxes running AOSP, plays video ads in hidden windows while impersonating legitimate streaming apps, sends fraudulent server-side ad insertion requests, and enrols devices in residential proxy networks, including PXYEDGE, which HUMAN describes as the successor to IpMoYu. Infected devices fetch malware modules from public code repositories. Researchers linked the operation to a Chinese electronics manufacturer through domains, device checks, a factory-installed TV launcher and a repository maintainer; the manufacturer is not named in the coverage read here. A Google-led XCPE disruption, in which HUMAN took part, took down several BADBOX 3.0 C2 domains, and one malware repository was taken down by a party the coverage does not name. HUMAN says its systems now filter the fraudulent advertising traffic. PXYEDGE was advertised with about 200,000 proxy nodes, and HUMAN's monitoring saw unique connections peak near 340,000. No infected-device count for BADBOX 3.0 and no device firmware fix appear in the sources read. Users should buy certified Android devices from reputable manufacturers and keep Play Protect enabled.
What to do
- Treat generic AOSP Android TV boxes and cheap Android devices as untrusted; inventory, isolate, and remove or replace infected devices.
- Block known BADBOX 3.0 C2 domains, malware repository URLs, and PXYEDGE/residential proxy endpoints; monitor egress for proxy and ad-fraud traffic.
- Filter fraudulent CTV/SSAI bid requests and monitor ad platforms for spoofed streaming-app traffic.
- Require certified Android devices and active Play Protect; prohibit uncertified devices on corporate networks.
- Segment IoT and streaming devices and restrict outbound access to only required services.
- Review ad-fraud and proxy-abuse logs and notify partners if traffic originates from your network.
Sources
All live incidents on Threat Watch