LIVE · cybersecurity feed
Live wire
CVE-2024-3848 · LFProjects MLflow Path Traversal Vulnerability Added To VulnCheck KEVCVE-2026-118267 · WPDataAccess Incorrect Authorization Flaw Exploited Same Day As DisclosureCVE-2026-118066 · LatePoint Improper Authentication Vulnerability Exploited On Day Of DisclosureCVE-2026-132224 · Optimizely Web Experimentation Flaw Exploited Same Day as DisclosureCVE-2026-133968 · Project-MONIA MONAI Label Path Traversal Exploited On Disclosure DateCairn AI Framework Used in Autonomous Zero-Day ExploitationAmazon: China-Linked Hackers’ AI Agents Exploited Medical Software Zero-DayCVE-2026-129975 · GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP KeysCVE-2026-129448 · Hackers Exploit Critical VMware, Cisco, and Apache Flaws as Espionage Attacks EmergeCTO of ‘RansomwareHelp’ Indicted for Wire Fraud
malware

BADBOX 3.0 botnet returns with record-breaking 40 billion daily ad requests

The BADBOX botnet has re-emerged in a third iteration, reaching unprecedented levels of activity by generating approximately 40 billion fraudulent advertising bid requests every day. Researchers at HUMAN, who identified and worked to disrupt this latest variant, report that BADBOX 3.0 now stands as the largest ad-fraud operation documented by daily volume. This surge in activity accounts for…

ZeroDay News ·

Source: BleepingComputer

The BADBOX botnet has re-emerged in a third iteration, reaching unprecedented levels of activity by generating approximately 40 billion fraudulent advertising bid requests every day. Researchers at HUMAN, who identified and worked to disrupt this latest variant, report that BADBOX 3.0 now stands as the largest ad-fraud operation documented by daily volume. This surge in activity accounts for more than 4% of all observed connected TV traffic, exceeding the volume of the previous record-holder, VASTFLUX, by more than three times.

The botnet’s history dates back to early 2023, when it was first identified on T95 Android TV boxes purchased through Amazon. By December 2024, German cybersecurity authorities issued warnings regarding tens of thousands of infected units. A significant disruption effort occurred in March 2025, involving HUMAN and the Shadowserver Foundation, which successfully severed the connection between more than 500,000 devices and their command-and-control servers. Google also removed 24 malicious applications from the Play Store and subsequently initiated legal action against the operators, estimating that the previous version, BADBOX 2.0, had compromised over 10 million Android-based devices by April 2025.

Despite these interventions, the operators have rebuilt the infrastructure, utilizing a persistent modus operandi that targets low-cost Android Open Source Project (AOSP) devices, including tablets, phones, and streaming boxes. The malware functions by running video advertisements in hidden windows while spoofing legitimate streaming applications to mask the fraudulent requests. Furthermore, the botnet employs server-side ad insertion techniques to deceive advertisers into paying for impressions that never occurred on an actual device.

A key component of the BADBOX 3.0 operation is the unauthorized enrollment of infected devices into residential proxy networks. Researchers identified a service known as PXYEDGE, which they characterize as a rebranded successor to the IpMoYu network previously associated with BADBOX 2.0. While PXYEDGE marketed roughly 200,000 proxy nodes, monitoring data indicates that the network actually maintained peak connections of approximately 340,000. These proxies are used to route fraudulent traffic, helping the botnet bypass anti-abuse filters by mimicking legitimate residential internet connections.

The investigation has linked the malware to a specific Chinese electronics manufacturer. Evidence for this attribution includes domain registrations, device-specific code checks, a factory-installed TV launcher, and the identity of a repository maintainer. To maintain operational resilience, the malware fetches modules from public code repositories and mirrors payloads across multiple hosting platforms, ensuring that the botnet can survive individual takedown attempts.

Recent mitigation efforts have included a coordinated operation between HUMAN and Google to disrupt the related XCPE malware, which resulted in the seizure of multiple command-and-control domains utilized by BADBOX 3.0. Additionally, researchers have successfully taken down one of the primary malware repositories and implemented traffic filtering to block fraudulent requests associated with the botnet.

Despite these technical disruptions, researchers caution that the operators have historically demonstrated an ability to adapt and rebuild. The botnet remains a significant threat to the advertising ecosystem and device security. Experts recommend that consumers mitigate the risk of infection by purchasing only certified Android devices from reputable manufacturers and ensuring that Google Play Protect remains active on all hardware.

malware
ShareXLinkedInWhatsAppFacebook

More News

view all →
patch

Weekly Update 531: Optimizely. Script Dependencies & Third Parties

A recent disclosure notice regarding Optimizely has highlighted ongoing concerns surrounding the security of third-party script dependencies. The incident underscores a growing trend where organizations point to external vendors when explaining security lapses, a practice that critics argue serves to deflect institutional accountability rather than addressing the underlying technical risks.

nation-state

FBI Investigating Apparent Hack of Its Key National Criminal Justice Database, AP Source Says

The Federal Bureau of Investigation is currently conducting an investigation into a potential security breach involving the National Crime Information Center, a critical repository of criminal justice data. The database, which is managed by the FBI, serves as a centralized resource for federal, state, and local law enforcement agencies. It contains sensitive information including records on…

breach

Rackspace Spot breach let hackers access customer Kubernetes secrets

Rackspace has confirmed a security breach affecting its Rackspace Spot cloud platform, a service designed for managing containerized applications through Kubernetes. The unauthorized access occurred on November 17, 2026, spanning a window from approximately 00:20 to 22:00 UTC. The company discovered the intrusion on November 18 following a report from a customer and subsequently verified that…

CVE-2024-3848high

LFProjects MLflow Path Traversal Vulnerability Added To VulnCheck KEV

The LFProjects MLflow path traversal vulnerability, CVE-2024-3848, has been added to the VulnCheck KEV catalogue, 894 days after its initial publication.

CVE-2026-118267high

WPDataAccess Incorrect Authorization Flaw Exploited Same Day As Disclosure

The wp_data_access plugin for WordPress faces active exploitation following a zero-day disclosure, yet it remains absent from major federal vulnerability catalogues.

CVE-2026-118066high

LatePoint Improper Authentication Vulnerability Exploited On Day Of Disclosure

The LatePoint plugin for WordPress is currently under exploitation, with the vulnerability appearing in the VulnCheck KEV catalogue on the same day it was published.