Incident Score: Analysis & Impact (DJIJPMTELGOO1789086449)
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 DJIJPMTELGOO1789086449.
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: 5254, the industry type: IT Services and IT Consulting and the number of employees: 185 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 336 and after the incident was 295 with a difference of -41 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 recently reported "Google Play Strengthens Security in 2025, Multi-Stage Phishing Campaign, Critical Flaws in BMC FootPrints, SnappyClient C2 Framework, LiveChat Phishing, GitHub Secrets Exposure, The Gentlemen RaaS, WhatsApp Alphanumeric Passwords, Malicious Packagist Themes, DJI API Flaw, CVE Exploitation Trends, Teams Phishing, EU CSAM Rules, Emerging Threats", a noteworthy cybersecurity incident.
Multiple cyber incidents reported in 2025, including Google Play's security enhancements, phishing campaigns, critical vulnerabilities, malware frameworks, data breaches, ransomware operations, and emerging threats.
The disruption is felt across the environment, affecting Android Apps, BMC FootPrints ITSM and GitHub Repositories, and exposing User Credentials, Credit Card Details and MFA Codes, with nearly ['28.65 million GitHub secrets', '24,088 MCP-related secrets'] records at risk.
In response, moved swiftly to contain the threat with measures like App Removal, Account Bans and API Patching, and began remediation that includes Vulnerability Patching, AI-Based Detection and Fraud Protection Expansion.
The case underscores how and recommending next steps like Enhance AI-based threat detection, Implement alphanumeric passwords for 2FA and Patch critical vulnerabilities promptly.
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 Phishing: Spearphishing Link (T1566.002) with high confidence (90%), supported by evidence indicating multi-chain redirect tactic, leveraging Cisco’s infrastructure and trusted services, Exploit Public-Facing Application (T1190) with moderate to high confidence (80%), supported by evidence indicating critical Flaws in BMC FootPrints ITSM Enable Pre-Auth Remote Code Execution, Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with moderate to high confidence (70%), supported by evidence indicating six trojanized Packagist packages, posing as OphimCMS themes, and Phishing: Spearphishing Attachment (T1566.001) with moderate to high confidence (70%), supported by evidence indicating teams Phishing Campaigns Impersonate IT Staff for Remote Access. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (80%), supported by evidence indicating pre-authentication remote code execution (RCE) in BMC FootPrints and User Execution: Malicious File (T1204.002) with moderate to high confidence (70%), supported by evidence indicating snappyClient distributed via a fake Telefónica website. Under the Persistence tactic, the analysis identified Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with moderate confidence (60%), supported by evidence indicating snappyClient employs evasion techniques like transacted hollowing. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (80%), supported by evidence indicating authentication bypass (CVE-2025-71257) in BMC FootPrints. Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with high confidence (90%), supported by evidence indicating snappyClient uses AMSI bypass, Heaven’s Gate, direct system calls, Deobfuscate/Decode Files or Information (T1140) with moderate to high confidence (70%), supported by evidence indicating aOT-compiled malware evades analysis by stripping .NET metadata, and Subvert Trust Controls: Mark-of-the-Web Bypass (T1553.005) with moderate confidence (60%), supported by evidence indicating cloudflare-based human validation step to evade security filters. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with high confidence (90%), supported by evidence indicating snappyClient steals data from browsers, extensions, and applications, Adversary-in-the-Middle: LLMNR/NBT-NS Poisoning and SMB Relay (T1557.001) with moderate confidence (60%), supported by evidence indicating liveChat phishing campaign to harvest credentials, credit card details, and Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (90%), supported by evidence indicating 28.65 million new secrets exposed in public GitHub commits. Under the Discovery tactic, the analysis identified Account Discovery: Local Account (T1087.001) with moderate to high confidence (70%), supported by evidence indicating snappyClient targets browser data and extensions for credential discovery. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating snappyClient steals data from browsers, extensions, and applications and Automated Collection (T1119) with moderate to high confidence (80%), supported by evidence indicating malicious Packagist themes exfiltrate URLs and inject ads. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with high confidence (90%), supported by evidence indicating snappyClient such as A Stealthy C2 Framework Targeting Cryptocurrency Theft. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating snappyClient steals data from browsers, extensions, and applications and Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (70%), supported by evidence indicating malicious Packagist themes exfiltrate URLs and redirect users. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate confidence (50%), supported by evidence indicating the Gentlemen RaaS group emerged in mid-2025 and Defacement: Internal Defacement (T1491.001) with moderate confidence (60%), supported by evidence indicating malicious Packagist themes inject ads and redirect users. 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/DJIJPMTELGOO1789086449
- Google Play CyberSecurity Rating page: https://www.rankiteo.com/company/google-play
- Google Play Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/djijpmtelgoo1789086449-telefnica-jpmorgan-chase-google-dji-cyber-attack-september-2025/
- Google Play CyberSecurity Score History: https://www.rankiteo.com/company/google-play/history
- Google Play CyberSecurity Incident Source: https://thehackernews.com/2026/03/threatsday-bulletin-fortigate-raas.html
- 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