Incident Score: Analysis & Impact (MICISR1784565175)
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 Microsoft Threat Intelligence'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 Microsoft Threat Intelligence 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 Microsoft Threat Intelligence breach identified under incident ID MICISR1784565175.
The analysis begins with a detailed overview of Microsoft Threat Intelligence's information like the linkedin page: https://www.linkedin.com/company/microsoft-threat-intelligence, the number of followers: 128397, the industry type: Computer and Network Security and the number of employees: None 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 412 and after the incident was 393 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 Microsoft Threat Intelligence and their customers.
On 03 June 2026, Israeli organization disclosed Espionage issues under the banner "HollowGraph: Espionage Malware Hijacks Microsoft 365 Calendars for Stealthy C2 Operations".
Security researchers at Group-IB have uncovered a novel espionage implant, HollowGraph, which leverages a compromised Microsoft 365 calendar as a command-and-control (C2) channel.
The disruption is felt across the environment, affecting Microsoft 365 calendars, Entra ID (Azure AD), and exposing Stolen files, Entra ID credentials.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing, teams are taking away lessons such as HollowGraph demonstrates the abuse of trusted cloud services (Microsoft 365) for C2 operations, highlighting the need for scrutiny of unusual calendar activity and OAuth permissions, and recommending next steps like Monitor calendar events with unusual dates (e.g., 2050-05-13) or GUID-based subjects, Audit OAuth app permissions and Entra ID token activity for anomalies and Investigate frequent DNS queries to suspicious domains (e.g., cloudlanecdn[.]com).
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: Cloud Accounts (T1078.004) with high confidence (90%), with evidence including compromised Microsoft 365 account with Graph API access, and entra ID (Azure AD) credentials stored in logAzure.txt. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), supported by evidence indicating hollowGraph malware, a .NET DLL, evades detection. Under the Persistence tactic, the analysis identified Create Account: Cloud Account (T1136.003) with moderate to high confidence (70%), supported by evidence indicating entra ID credentials (tenant ID, client ID, client secret) refreshed via DNS queries and Account Manipulation: Additional Cloud Credentials (T1098.001) with moderate to high confidence (80%), supported by evidence indicating newly created client secrets or anomalous Entra ID token activity. Under the Defense Evasion tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating abuses legitimate Microsoft 365 functionality for C2 operations, Hide Artifacts: Email Hiding Rules (T1564.008) with high confidence (90%), supported by evidence indicating calendar events dated to 2050 to hide from typical user activity, and Obfuscated Files or Information (T1027) with moderate to high confidence (80%), supported by evidence indicating hybrid RSA and AES-256 encryption for incoming/outgoing traffic. Under the Command and Control tactic, the analysis identified Web Service: Bidirectional Communication (T1102.002) with high confidence (90%), supported by evidence indicating uses Microsoft 365 calendar as a dead drop for C2 via Graph API and Application Layer Protocol: DNS (T1071.004) with moderate to high confidence (80%), supported by evidence indicating dNS queries to cloudlanecdn.com for credential refresh. Under the Exfiltration tactic, the analysis identified Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with high confidence (90%), supported by evidence indicating exfiltrates stolen data via calendar events as attachments and Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating data exfiltration via encrypted files in far-future calendar events. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating stolen files and Entra ID credentials compromised. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating entra ID credentials (tenant ID, client ID, client secret) stored in logAzure.txt. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Microsoft Threat Intelligence Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/microsoft-threat-intelligence/incident/MICISR1784565175
- Microsoft Threat Intelligence CyberSecurity Rating page: https://www.rankiteo.com/company/microsoft-threat-intelligence
- Microsoft Threat Intelligence Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/micisr1784565175-microsoft-israeli-organization-cyber-attack-june-2026/
- Microsoft Threat Intelligence CyberSecurity Score History: https://www.rankiteo.com/company/microsoft-threat-intelligence/history
- Microsoft Threat Intelligence CyberSecurity Incident Source: https://thehackernews.com/2026/07/hollowgraph-malware-hides-c2-and-stolen.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