24 million (downloads)
Security researchers have dismantled a massive Android ad fraud operation, dubbed "Trapdoor," that leveraged a complex network of 455 malicious applications on the Google Play Store to generate hundreds of millions of fraudulent ad requests daily. The campaign, which achieved over 24 million downloads, employed a multi-stage infection process to create a self-sustaining revenue loop. Harmless-looking first-stage apps would use deceptive ads to lure users into installing secondary apps containing the core ad fraud payload. This payload would then run in the background, loading hidden web views to simulate user clicks on ads. The operation was notable for its scale, at one point generating 659 million fraudulent bid requests in a single day, and its clever evasion tactics, which involved activating the malicious payload only on devices acquired through specific advertising campaigns.
"Trapdoor" was a highly organized and technically sophisticated mobile ad fraud campaign. Its primary goal was to generate illicit revenue by defrauding mobile advertising networks.
WebView) to load attacker-controlled web pages filled with ads and programmatically click on them.The Trapdoor operation demonstrates a deep understanding of the mobile advertising ecosystem.
T1456 - Drive-by Compromise) to coerce users into granting more permissions or installing additional malicious software.WebView components to load web pages without the user's knowledge. It then uses JavaScript to simulate user behavior, such as scrolling and clicking on ad banners, to register fraudulent impressions and clicks with ad networks.T1476 - Deliver Malicious App via Other Means: The Stage 1 app delivering the Stage 2 app.T1634 - Abuse of Legitimate Apps or Services: Abusing the mobile attribution SDK to control payload activation.T1419 - Ad Fraud: The primary objective and action of the malware.T1625 - Hidden Service Execution: Running the ad-clicking activity in hidden background browser views.The articles mentioned 455 malicious apps but did not list their specific package names.
On a mobile device, security teams or users can look for the following:
process_namecom.utility.pdfviewernetwork_traffic_patternHigh background data usageotherRapid battery drainlog_sourceAndroid LogcatWebView instances without a visible UI.WebView activity.Use a reputable Mobile Threat Defense solution to scan for and detect malicious applications and their behavior.
For corporate devices, use an MDM to create an allowlist of approved applications, preventing the installation of unauthorized apps from the Play Store.
Educate users to be skeptical of apps that demand excessive permissions or use deceptive pop-ups to push other installations.
On mobile devices, Process Analysis via a Mobile Threat Defense (MTD) solution is key to detecting 'Trapdoor'. The MTD agent can monitor application behavior in the background. It should be configured to detect when an application creates hidden WebView components that are not part of any visible user activity. Furthermore, it can analyze the network traffic originating from these hidden processes. A rule could be set to alert when an app that is not in the foreground is generating a high volume of traffic to known advertising networks. This behavioral approach is effective because it focuses on the malicious action (hidden ad clicking) rather than a static signature, allowing it to catch new variants of the fraudware.
Executable Denylisting, in the context of Android, translates to application blocklisting. Once the 455 apps associated with 'Trapdoor' were identified by HUMAN, their package names became high-fidelity indicators of compromise. In an enterprise environment, a Mobile Device Management (MDM) or Unified Endpoint Management (UEM) solution should be used to push a blocklist policy to all managed devices. This policy would prevent the installation of these apps or automatically uninstall them if they are already present. While this is a reactive measure, it's crucial for containing a known threat and cleaning up an infected device population. Google Play Protect performs a similar function for the broader consumer ecosystem.
To proactively defend against threats like 'Trapdoor', app stores and security vendors must use Dynamic Analysis sandboxes. The key to defeating 'Trapdoor's' evasion was to replicate the entry vector. The sandbox environment must be able to simulate an install originating from a paid advertising campaign. By instrumenting the device to report a specific attribution source, the sandbox could trigger the dormant payload. Once active, the dynamic analysis engine would observe the creation of hidden WebViews, the programmatic clicking, and the high volume of ad traffic, definitively identifying the app as malicious. This advanced sandboxing is essential for app vetting processes to defeat sophisticated, environment-aware malware.
Security researchers begin to publicly disclose the 'Trapdoor' ad fraud campaign.

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.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.