7.3 million downloads
Security researchers at ESET have uncovered a large-scale fleeceware campaign on the Google Play Store, which they have dubbed "CallPhantom." The operation involved 28 malicious applications that successfully duped over 7.3 million users into downloading them. These apps, primarily targeting users in India and the Asia-Pacific region, lured victims with the false promise of being able to retrieve the call history and messages of any phone number. To access this non-existent service, users were tricked into paying for a subscription. The apps would then display fake, randomly generated data. The apps have since been removed by Google, but the campaign's success highlights the ongoing threat of fraudulent apps on official marketplaces.
The CallPhantom campaign is a classic example of fleeceware—apps that are not technically malware (they don't steal data or damage the device) but use deceptive practices to trick users into paying for worthless or non-existent services. The apps' core deception was the claim that they could provide access to private call and message logs, a technically infeasible feature for a third-party app. To enhance their credibility, at least one app masqueraded as an official government application, using the developer name "Indian gov.in." This social engineering tactic, combined with the allure of the promised functionality, led to millions of downloads and subsequent fraudulent charges to users.
The CallPhantom apps are not sophisticated from a malware perspective but are effective as a scam. Their operation can be broken down into a few key steps:
T1475 - Legitimate Software).T1036 - Masquerading) to evade user suspicion.T1488 - Financial Theft). The apps generate random, fake data to maintain the illusion of functionality for a short period.The direct impact is financial loss for the 7.3 million users who downloaded and potentially paid for subscriptions to these fraudulent apps. While the individual financial loss may be small, the collective profit for the scammers is substantial. The incident also damages user trust in the Google Play Store's vetting process and highlights the difficulty in policing app marketplaces for scams that do not involve traditional malware. For Google, it represents a reputational challenge and reinforces the need for more stringent review processes to detect and remove fleeceware.
The source articles mentioned the names of some of the fraudulent apps, which can be considered IOCs:
file_nameCall history : any number detafile_nameCall History of Any NumberFor mobile device management administrators and users, the following are red flags for fleeceware and other malicious apps:
string_patternstring_patternotherotherM1017 - User Training). Teach users to be highly skeptical of apps that make claims that sound too good to be true. Train them to read reviews, check permissions, and verify the developer's reputation before installing.The primary defense against fleeceware is educating users to be skeptical of app claims and to perform due diligence before installing.
Using MDM solutions to create an allowlist of approved applications for corporate devices can prevent the installation of fraudulent software.
In a corporate environment, the most effective way to prevent incidents like CallPhantom is through Executable Allowlisting, managed by a Mobile Device Management (MDM) or Unified Endpoint Management (UEM) solution. Instead of allowing users to install any app from the public Google Play Store, the organization should create a curated enterprise app store containing only vetted, approved applications required for business functions. This policy would prevent employees from downloading and installing the 28 fraudulent CallPhantom apps, completely neutralizing the threat on managed devices. This shifts the security model from a reactive, user-dependent approach to a proactive, policy-enforced one.

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.