Incident Score: Analysis & Impact (ONT1787063426)
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 Ontinue'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 Ontinue 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 Ontinue breach identified under incident ID ONT1787063426.
The analysis begins with a detailed overview of Ontinue's information like the linkedin page: https://www.linkedin.com/company/ontinue, the number of followers: 7415, the industry type: Computer and Network Security and the number of employees: 214 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 752 and after the incident was 735 with a difference of -17 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 Ontinue and their customers.
On 01 July 2026, a cybersecurity incident called "TWINLOOT Python Implant Framework Exploits Microsoft Services for Stealthy C2 Operations" came to light.
Cybersecurity researchers at Ontinue uncovered TWINLOOT, a previously undocumented Python-based implant framework designed to conceal its command-and-control (C2) infrastructure within trusted Microsoft services.
The disruption is felt across the environment, affecting Windows Systems, and exposing Credentials and Sensitive System Data.
Formal response steps have not been shared publicly yet.
The case underscores how Ongoing, teams are taking away lessons such as The incident highlights the growing trend of threat actors abusing trusted cloud services (e.g., Microsoft Graph API, SharePoint, Teams TURN servers) for C2 operations, making detection challenging. The use of headless browsers and novel persistence techniques (e.g., Swarmer Registry keys) underscores the need for enhanced monitoring of legitimate service interactions, and recommending next steps like Implement strict Microsoft Teams message filtering to block suspicious PowerShell execution requests, Monitor and restrict access to Microsoft Graph API and SharePoint Online for unusual activity and Deploy behavioral detection for headless browser processes (e.g., Edge) interacting with external services.
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 via Service (T1566.003) with high confidence (90%), with evidence including social engineering lure via Microsoft Teams, and tricks victims into executing a PowerShell command. Under the Execution tactic, the analysis identified Command and Scripting Interpreter: PowerShell (T1059.001) with high confidence (95%), supported by evidence indicating powerShell command that downloads a 39 MB compiled Python payload and User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), supported by evidence indicating victims into executing a PowerShell command that downloads payload. Under the Persistence tactic, the analysis identified Event Triggered Execution: Component Object Model Hijacking (T1546.015) with moderate to high confidence (85%), supported by evidence indicating typeLib COM scriptlet hijacking for persistence, Scheduled Task/Job: Scheduled Task (T1053.005) with moderate to high confidence (80%), supported by evidence indicating ghostTask-style TaskCache manipulation for persistence, and Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder (T1547.001) with moderate to high confidence (75%), supported by evidence indicating novel Registry-based method using Swarmer tool for HKCU keys. Under the Privilege Escalation tactic, the analysis identified Event Triggered Execution: Component Object Model Hijacking (T1546.015) with moderate to high confidence (70%), supported by evidence indicating typeLib COM scriptlet hijacking for privilege escalation. Under the Defense Evasion tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating authenticates to attacker-controlled Azure tenant via Microsoft Graph API, Deobfuscate/Decode Files or Information (T1140) with moderate to high confidence (80%), supported by evidence indicating pyArmor-hardened to resist analysis, Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (85%), supported by evidence indicating headless Edge browser to ferry Graph API traffic, blending with normal behavior, and Hide Artifacts: Email Hiding Rules (T1564.008) with moderate to high confidence (70%), supported by evidence indicating conceal its C2 infrastructure within trusted Microsoft services. Under the Credential Access tactic, the analysis identified Input Capture: GUI Input Capture (T1056.002) with high confidence (90%), supported by evidence indicating fake lock screen prompts triggered by credz_waiting command for credential harvesting and Credentials from Password Stores (T1555) with moderate to high confidence (70%), supported by evidence indicating captures Windows credentials through fake lock screen prompts. Under the Discovery tactic, the analysis identified Account Discovery: Local Account (T1087.001) with moderate to high confidence (70%), supported by evidence indicating lateral movement via RDP/WinRM suggests account discovery and File and Directory Discovery (T1083) with moderate confidence (60%), supported by evidence indicating modular design implies discovery of system data. Under the Lateral Movement tactic, the analysis identified Remote Services: Remote Desktop Protocol (T1021.001) with high confidence (90%), supported by evidence indicating sOCKS5 tunnel abused for RDP-based lateral movement, Remote Services: Windows Remote Management (T1021.006) with high confidence (90%), supported by evidence indicating sOCKS5 tunnel abused for WinRM-based lateral movement, and Proxy: External Proxy (T1090.002) with moderate to high confidence (85%), supported by evidence indicating sOCKS5 proxy over WebRTC DataChannels via Teams TURN servers. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating data exfiltration and arbitrary command execution via SharePoint and Screen Capture (T1113) with moderate to high confidence (70%), supported by evidence indicating fake lock screen prompts for credential harvesting. Under the Command and Control tactic, the analysis identified Ingress Tool Transfer (T1105) with high confidence (90%), supported by evidence indicating downloads a 39 MB compiled Python payload (bootstrap-fat.pyc), Application Layer Protocol: Web Protocols (T1071.001) with high confidence (95%), supported by evidence indicating sharePoint Online and Microsoft Graph API for C2 communications, Proxy: Multi-hop Proxy (T1090.003) with moderate to high confidence (80%), supported by evidence indicating sOCKS5 proxy over WebRTC DataChannels via Teams TURN servers, and Encrypted Channel: Asymmetric Cryptography (T1573.002) with moderate to high confidence (70%), supported by evidence indicating direct TLS/WebSocket connection for C2. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating data exfiltration to attacker’s SharePoint drive and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with high confidence (95%), supported by evidence indicating exfiltrates credentials to attacker’s SharePoint drive. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Ontinue Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/ontinue/incident/ONT1787063426
- Ontinue CyberSecurity Rating page: https://www.rankiteo.com/company/ontinue
- Ontinue Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/ont1787063426-ontinue-cyber-attack-july-2026/
- Ontinue CyberSecurity Score History: https://www.rankiteo.com/company/ontinue/history
- Ontinue CyberSecurity Incident Source: https://thehackernews.com/2026/08/twinloot-abuses-sharepoint-and-teams-to.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