Incident Score: Analysis & Impact (MATHINOKT1769712133)
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 Match Group'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 Match Group 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 Match Group breach identified under incident ID MATHINOKT1769712133.
The analysis begins with a detailed overview of Match Group's information like the linkedin page: https://www.linkedin.com/company/matchgroup, the number of followers: 33343, the industry type: Software Development and the number of employees: 3203 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 728 and after the incident was 701 with a difference of -27 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 Match Group and their customers.
Match Group recently reported "Match Group Data Breach After ShinyHunters Leaks 10 Million User Records", a noteworthy cybersecurity incident.
Match Group, the parent company behind popular dating platforms Tinder, Match.com, Meetic, OkCupid, and Hinge, confirmed a cybersecurity incident involving the theft of user data.
The disruption is felt across the environment, affecting AppsFlyer marketing analytics, Google Drive and Dropbox, and exposing 10 million records, with nearly 10 million records at risk.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Terminated unauthorized access, and stakeholders are being briefed through Notified affected individuals as appropriate.
The case underscores how Ongoing, teams are taking away lessons such as Need for phishing-resistant multi-factor authentication (MFA), such as FIDO2 security keys or passkeys, strict app authorization policies, and monitoring for anomalous API activity, and recommending next steps like Implement phishing-resistant MFA (FIDO2 security keys/passkeys), Enforce strict app authorization policies and Monitor for anomalous API activity, with advisories going out to stakeholders covering Affected individuals are being notified as appropriate.
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%), with evidence including social engineering campaign targeting single sign-on (SSO) accounts, and phishing attempt used the domain *matchinternal.com* and Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), with evidence including compromised an Okta SSO account, and provided entry to AppsFlyer, Google Drive, and Dropbox. Under the Credential Access tactic, the analysis identified Modify Authentication Process: Multi-Factor Authentication (T1556.006) with moderate to high confidence (70%), with evidence including phishing-resistant MFA recommended post-incident, and okta SSO account compromised despite MFA and Brute Force: Password Guessing (T1110.001) with moderate confidence (50%), supported by evidence indicating social engineering likely bypassed MFA, but brute force not ruled out. Under the Persistence tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating okta SSO account used to access AppsFlyer, Google Drive, Dropbox. Under the Lateral Movement tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.004) with moderate to high confidence (80%), supported by evidence indicating okta SSO account provided entry to multiple cloud services. Under the Collection tactic, the analysis identified Data from Cloud Storage (T1530) with high confidence (90%), supported by evidence indicating 1.7 GB of files exfiltrated from Google Drive and Dropbox and Data from Information Repositories: Sharepoint (T1213.002) with moderate confidence (60%), supported by evidence indicating internal documents leaked, likely from cloud storage. Under the Exfiltration tactic, the analysis identified Transfer Data to Cloud Account (T1537) with moderate to high confidence (80%), supported by evidence indicating shinyHunters leaked 1.7 GB of compressed files and Exfiltration Over C2 Channel (T1041) with moderate to high confidence (70%), supported by evidence indicating 10 million records exfiltrated by ShinyHunters. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (80%), supported by evidence indicating okta SSO account used to bypass standard authentication and Hide Artifacts: Email Hiding Rules (T1564.008) with moderate confidence (50%), supported by evidence indicating phishing domain *matchinternal.com* likely evaded detection. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Match Group Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/matchgroup/incident/MATHINOKT1769712133
- Match Group CyberSecurity Rating page: https://www.rankiteo.com/company/matchgroup
- Match Group Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/mathinokt1769712133-okta-hinge-match-group-matchcom-okcupid-cyber-attack-january-2026/
- Match Group CyberSecurity Score History: https://www.rankiteo.com/company/matchgroup/history
- Match Group CyberSecurity Incident Source: https://www.bleepingcomputer.com/news/security/match-group-breach-exposes-data-from-hinge-tinder-okcupid-and-match/
- 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