Incident Score: Analysis & Impact (GOO1778157015)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Google Play's Cyber Attack and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Google Play Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Google Play breach identified under incident ID GOO1778157015.
The analysis begins with a detailed overview of Google Play's information like the linkedin page: https://www.linkedin.com/company/google-play, the number of followers: 4814, the industry type: IT Services and IT Consulting and the number of employees: 184 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 367 and after the incident was 343 with a difference of -24 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Google Play and their customers.
Google Play Store users recently reported "Fraudulent 'CallPhantom' Apps on Google Play Scammed Millions with Fake Call History Data", a noteworthy cybersecurity incident.
A sophisticated fraud campaign involving 28 malicious Android apps collectively dubbed *CallPhantom* deceived over 7.3 million users before being removed from Google Play in December 2025.
The disruption is felt across the environment, affecting Android devices of 7.3 million users, and exposing None (fabricated data only), plus an estimated financial loss of Up to $80 per victim (subscription fees).
In response, moved swiftly to contain the threat with measures like Google removed the 28 malicious apps from Google Play, and began remediation that includes Google canceled subscriptions tied to its official billing system.
The case underscores how Closed (apps removed), teams are taking away lessons such as Deceptive apps can evade detection by dynamically fetching payment details and using third-party payment methods to bypass platform protections. Users should be cautious of apps promising unrealistic functionalities, and recommending next steps like Enhance Google Play Store vetting processes for apps offering sensitive services (e.g., call history access), Improve detection of apps using dynamic payment systems to evade platform policies and Educate users on recognizing deceptive subscription models and verifying app legitimacy.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Deliver Malicious App via Authorized App Store (T1475) with high confidence (90%), supported by evidence indicating 28 fake call history apps on Google Play with 7.3M+ downloads. Under the Execution tactic, the analysis identified Download New Code at Runtime (T1407) with moderate to high confidence (70%), supported by evidence indicating dynamically fetching payment details from Firebase real-time databases. Under the Defense Evasion tactic, the analysis identified Generate Fake Telemetry (T1622) with high confidence (90%), supported by evidence indicating displaying partial, hardcoded call logs with fake names/timestamps and Obfuscated Files or Information (T1406) with moderate to high confidence (70%), supported by evidence indicating fabricated data to create illusion of functionality. Under the Collection tactic, the analysis identified Input Capture (T1417) with moderate to high confidence (80%), supported by evidence indicating embedded payment forms within the app for UPI/card transactions. Under the Exfiltration tactic, the analysis identified Transfer Data to Cloud Account (T1537) with moderate to high confidence (70%), supported by evidence indicating payment details fetched from Firebase real-time databases. Under the Impact tactic, the analysis identified Financial Theft (T1472) with high confidence (90%), supported by evidence indicating subscription fees up to $80 per victim, 7.3M users affected. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Google Play Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/google-play/incident/GOO1778157015
- Google Play CyberSecurity Rating page: https://www.rankiteo.com/company/google-play
- Google Play Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/goo1778157015-google-cyber-attack-december-2025/
- Google Play CyberSecurity Score History: https://www.rankiteo.com/company/google-play/history
- Google Play CyberSecurity Incident Source: https://cybersecuritynews.com/28-fake-call-history-apps-on-google-play-with-7-3m-downloads/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf