Incident Score: Analysis & Impact (MICGOO1772628247)
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 Workspace'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 Workspace 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 Workspace breach identified under incident ID MICGOO1772628247.
The analysis begins with a detailed overview of Google Workspace's information like the linkedin page: https://www.linkedin.com/company/googleworkspace, the number of followers: 725220, the industry type: Software Development and the number of employees: 3 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 733 and after the incident was 712 with a difference of -21 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 Workspace and their customers.
Government and public-sector organizations recently reported "Sophisticated Phishing Campaigns Abusing OAuth 2.0 Redirects", a noteworthy cybersecurity incident.
Microsoft has identified a series of phishing attacks targeting government and public-sector organizations by exploiting OAuth 2.0’s redirection features in Microsoft Entra ID and Google Workspace.
The disruption is felt across the environment, affecting Microsoft Entra ID and Google Workspace.
In response, and began remediation that includes OAuth governance (app audits, access controls), Enforce Conditional Access and identity protection and Use XDR for telemetry and hunting.
The case underscores how teams are taking away lessons such as The campaign underscores the growing trend of protocol abuse in phishing, where attackers leverage legitimate features to evade detection, and recommending next steps like Regularly audit overprivileged OAuth applications, Enforce Conditional Access and identity protection and Use XDR for telemetry and hunting to detect anomalies like PowerShell execution from LNK files or DLL sideloading.
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 (T1566) with high confidence (95%), supported by evidence indicating phishing emails disguised as e-signature requests, Teams invites, or password resets and Phishing: Spearphishing Link (T1566.002) with high confidence (90%), supported by evidence indicating lure victims into clicking links that trigger a silent OAuth flow. Under the Execution tactic, the analysis identified User Execution: Malicious Link (T1204.001) with high confidence (90%), supported by evidence indicating victims are...prompted to download a ZIP file containing a malicious LNK file and Command and Scripting Interpreter: PowerShell (T1059.001) with high confidence (90%), supported by evidence indicating lNK file...executes PowerShell for host reconnaissance. Under the Persistence tactic, the analysis identified Create Account: Cloud Account (T1136.003) with moderate to high confidence (80%), supported by evidence indicating threat actors register malicious apps in their tenant. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with high confidence (90%), supported by evidence indicating abusing OAuth 2.0’s redirection features...to deliver malware, Exploitation for Defense Evasion (T1211) with moderate to high confidence (80%), supported by evidence indicating manipulating parameters like `prompt=none` and `scope=invalid` to force error redirects, and Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (85%), supported by evidence indicating sideloads `crashhandler.dll` via a legitimate `steam_monitor.exe` process. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating redirected to tools like EvilProxy for session hijacking and Adversary-in-the-Middle: ARP Poisoning (T1557.002) with moderate to high confidence (70%), supported by evidence indicating evilProxy for session hijacking. Under the Discovery tactic, the analysis identified Account Discovery: Cloud Account (T1087.004) with moderate to high confidence (80%), supported by evidence indicating powerShell for host reconnaissance. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (85%), supported by evidence indicating establish command-and-control (C2) communication and Ingress Tool Transfer (T1105) with moderate to high confidence (80%), supported by evidence indicating sideloads `crashhandler.dll` via `steam_monitor.exe`. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating session hijacking via EvilProxy. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Google Workspace Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/googleworkspace/incident/MICGOO1772628247
- Google Workspace CyberSecurity Rating page: https://www.rankiteo.com/company/googleworkspace
- Google Workspace Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/micgoo1772628247-microsoft-google-cyber-attack-march-2026/
- Google Workspace CyberSecurity Score History: https://www.rankiteo.com/company/googleworkspace/history
- Google Workspace CyberSecurity Incident Source: https://cyberpress.org/microsoft-warns-oauth-in-entra-id/
- 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