Incident Score: Analysis & Impact (WORNOTGOOZOONIKTIN1777868873)
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 Breach 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 WORNOTGOOZOONIKTIN1777868873.
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 713 and after the incident was 552 with a difference of -161 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.
On 20 March 2026, Gmail disclosed Data Collection, Privacy Violation and Data Breach issues under the banner "Workplace Apps Collect Extensive User Data, Raising Privacy and Security Concerns".
A recent study by Incogni reveals that ten widely used workplace apps, including Gmail, Microsoft Teams, Zoom Workplace, Slack, and Notion, collect an average of 19 data points per app, with some sharing sensitive information with third parties.
The disruption is felt across the environment, affecting Gmail, Microsoft Teams and Zoom Workplace, and exposing Login Credentials, Email Addresses and Names, with nearly ['149 million (Gmail-related)', '17,000 (Slack)'] records at risk.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing, teams are taking away lessons such as The trade-offs between workplace productivity and data exposure highlight the need for stronger data protection measures, end-to-end encryption, and stricter third-party data sharing policies, and recommending next steps like Implement end-to-end encryption for sensitive communications, Limit third-party data sharing and tracking and Provide users with clear data deletion options.
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 Valid Accounts (T1078) with high confidence (90%), supported by evidence indicating attackers used stolen credentials to access accounts of over 17,000 Nikkei employees and Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating workday breaches linked to its Salesforce CRM. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), supported by evidence indicating 96-gigabyte database exposed due to infostealer malware on user devices. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with moderate to high confidence (80%), supported by evidence indicating 149 million login credentials exposed, 48 million tied to Gmail and OS Credential Dumping (T1003) with moderate to high confidence (70%), supported by evidence indicating infostealer malware on user devices. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating apps collect 19 data points per app, including location, app interactions, user IDs and Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating slack chat histories, Notion workspace content exposed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating data exfiltration confirmed in breaches and Transfer Data to Cloud Account (T1537) with moderate confidence (60%), supported by evidence indicating notion shares 8 data types with third parties, including advertising partners. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating lack of end-to-end encryption in Slack and Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (70%), supported by evidence indicating stolen credentials used to access corporate accounts. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating extensive data exposure may lead to misuse and Data Manipulation: Stored Data Manipulation (T1565.001) with moderate confidence (50%), supported by evidence indicating potential misuse of exposed employment records and payroll details. 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/WORNOTGOOZOONIKTIN1777868873
- Google Workspace CyberSecurity Rating page: https://www.rankiteo.com/company/googleworkspace
- Google Workspace Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/wornotgoozooniktin1777868873-notion-slack-google-zoom-nikkei-workday-breach-march-2026/
- Google Workspace CyberSecurity Score History: https://www.rankiteo.com/company/googleworkspace/history
- Google Workspace CyberSecurity Incident Source: https://www.helpnetsecurity.com/2026/05/04/workplace-apps-data-collection-privacy/
- 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