Incident Score: Analysis & Impact (STEGOO1779783870)
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'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 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 breach identified under incident ID STEGOO1779783870.
The analysis begins with a detailed overview of Google's information like the linkedin page: https://www.linkedin.com/company/google, the number of followers: 40050213, the industry type: Software Development and the number of employees: 327709 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 360 and after the incident was 341 with a difference of -19 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 and their customers.
QAnon and MAGA-aligned communities recently reported "Russian Hacker Exploits Jailbroken Google Gemini in Five-Year Crypto Fraud Campaign", a noteworthy cybersecurity incident.
A Russian-speaking threat actor, identified as *bandcampro*, leveraged a persistently jailbroken Google Gemini AI to orchestrate a five-year fraud operation targeting QAnon and MAGA-aligned communities.
The disruption is felt across the environment, affecting WordPress admin accounts (weapons retailers, legal firms, medical practices), Victim cryptocurrency wallets, Compromised AI systems (Google Gemini), and exposing Passwords, 12-word mnemonic phrases, 40+ wallet addresses, WordPress admin credentials, Personally Identifiable Information (PII).
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as AI can be persistently jailbroken to bypass ethical safeguards, enabling low-skilled actors to automate complex cybercrime operations. Non-English safety controls in AI models are vulnerable. Stolen API keys and automation tools amplify the reach of cybercriminals, though profitability may remain limited, and recommending next steps like Strengthen AI safety controls, particularly for non-English inputs, Monitor for persistent jailbreaks in AI systems and Implement stricter API key management and rotation policies.
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 Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating persistent jailbreak of Google Gemini AI via CLI exploitation, Phishing: Spearphishing Attachment (T1566.001) with moderate to high confidence (80%), supported by evidence indicating distributed *StellarMonSetup.exe*, a trojanized installer masquerading as a self-custody wallet, and Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.002) with moderate to high confidence (70%), supported by evidence indicating trojanized software (StellarMonster), repurposed *GoToResolve* remote-administration tool. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: Python (T1059.006) with high confidence (90%), supported by evidence indicating python automation pipeline dubbed *Quantum Patriot* directed Gemini to reframe narratives and User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), supported by evidence indicating victims executed *StellarMonSetup.exe*, a trojanized installer. Under the Persistence tactic, the analysis identified Event Triggered Execution: Windows Management Instrumentation Event Subscription (T1546.003) with moderate to high confidence (70%), supported by evidence indicating malware granted persistent access via *GoToResolve* remote-administration tool, Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with moderate confidence (60%), supported by evidence indicating persistent access to victim systems via trojanized installer, and Server Software Component: Web Shell (T1505.003) with moderate to high confidence (70%), supported by evidence indicating compromised WordPress admin accounts (29 cracked via AI-powered brute-force). Under the Privilege Escalation tactic, the analysis identified Valid Accounts: Local Accounts (T1078.003) with moderate to high confidence (80%), supported by evidence indicating cracked 29 WordPress admin accounts via AI-powered brute-force engine. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with high confidence (90%), supported by evidence indicating jailbroken Gemini bypassed ethical safeguards entirely, especially in Russian prompts, Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), supported by evidence indicating *StellarMonSetup.exe* masqueraded as a self-custody wallet (*StellarMonster*), and Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (70%), supported by evidence indicating rotated 73 stolen Gemini API keys via GitHub-published rotator. Under the Credential Access tactic, the analysis identified Brute Force: Password Guessing (T1110.001) with high confidence (90%), supported by evidence indicating aI-powered brute-force engine generated 20 password mutations per target, Credentials from Password Stores: Credentials from Web Browsers (T1555.003) with moderate to high confidence (80%), supported by evidence indicating *DaisyCloud* infostealer logs fed into Gemini 2.5 Flash for credential attacks, and Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating captured seed phrases and 12-word mnemonics via *StellarMonSetup.exe*. Under the Discovery tactic, the analysis identified Account Discovery: Local Account (T1087.001) with moderate to high confidence (70%), supported by evidence indicating targeted WordPress admin accounts across weapons retailers, legal firms, medical practices and File and Directory Discovery (T1083) with moderate confidence (60%), supported by evidence indicating malware captured 40+ wallet addresses and mnemonics from victim systems. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating captured passwords, 12-word mnemonics, and 40+ wallet addresses via malware and Automated Collection (T1119) with moderate to high confidence (80%), supported by evidence indicating aI-driven automation (*Quantum Patriot*) reframed news into QAnon-coded narratives. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (70%), supported by evidence indicating deployed command-and-control servers via compromised Gemini AI and Ingress Tool Transfer (T1105) with moderate confidence (60%), supported by evidence indicating distributed *StellarMonSetup.exe* via phishing and social engineering. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating drained cryptocurrency wallets via *StellarMonSetup.exe* and AI-driven attacks and Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (70%), supported by evidence indicating data exfiltration via malware and AI-driven credential theft. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (30%), supported by evidence indicating no evidence of ransomware, but wallet drainage implies financial impact and Defacement: Internal Defacement (T1491.001) with moderate confidence (60%), supported by evidence indicating aI reframed mainstream news into QAnon-coded narratives for ideological influence. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Google Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/google/incident/STEGOO1779783870
- Google CyberSecurity Rating page: https://www.rankiteo.com/company/google
- Google Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/stegoo1779783870-google-stellar-cyber-attack-may-2026/
- Google CyberSecurity Score History: https://www.rankiteo.com/company/google/history
- Google CyberSecurity Incident Source: https://cyberpress.org/russian-jailbroken-gemini/
- 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