Incident Score: Analysis & Impact (REV1789562336)
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 Revolut'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 Revolut 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 Revolut breach identified under incident ID REV1789562336.
The analysis begins with a detailed overview of Revolut's information like the linkedin page: https://www.linkedin.com/company/revolut, the number of followers: 2138749, the industry type: Financial Services and the number of employees: 19786 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 617 and after the incident was 566 with a difference of -51 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 Revolut and their customers.
Revolut recently reported "Revolut Data Breach Exposes 680 Customers in Sophisticated Social Engineering Attack", a noteworthy cybersecurity incident.
Revolut suffered a data breach after cybercriminals impersonated government officials using a compromised legitimate email account.
The disruption is felt across the environment, and exposing Passport details, identity documents, home addresses, bank account numbers, cryptocurrency activity, with nearly 680 records at risk.
In response, moved swiftly to contain the threat with measures like Blocked fraudulent email address.
The case underscores how Ongoing, teams are taking away lessons such as Security must extend beyond perimeter defenses; stricter verification of external requests and controlled disclosure of sensitive data are required. The incident highlights the growing threat of social engineering and AI-enabled fraud, and recommending next steps like Adopt decentralized identity verification, Implement blockchain-based credentials and Use hyperscale AI for real-time threat detection.
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 Link (T1566.002) with high confidence (90%), supported by evidence indicating cybercriminals impersonated government officials using a compromised legitimate email account and Trusted Relationship (T1199) with moderate to high confidence (80%), supported by evidence indicating exploited trust in official communication channels; compromised Italian government email system. Under the Credential Access tactic, the analysis identified Compromise Accounts: Email Accounts (T1586) with high confidence (90%), supported by evidence indicating attack originated from a hijacked Italian government email system used for secure legal communications. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating disclose sensitive customer information including passport details, identity documents, home addresses and Data from Local System (T1005) with moderate to high confidence (70%), supported by evidence indicating bank account numbers, and cryptocurrency activity affecting approximately 680 individuals. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating data breach exposing 680 customers; hackers later demanded a ransom and Exfiltration Over Web Service (T1567) with moderate confidence (60%), supported by evidence indicating threatening to publish the stolen information. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with moderate confidence (50%), supported by evidence indicating hackers later demanded a ransom, threatening to publish the stolen information and Defacement: Internal Defacement (T1491.001) with lower confidence (40%), supported by evidence indicating brand reputation impact such as High. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (70%), supported by evidence indicating compromised legitimate email account (Italian government email system). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Revolut Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/revolut/incident/REV1789562336
- Revolut CyberSecurity Rating page: https://www.rankiteo.com/company/revolut
- Revolut Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/rev1789562336-revolut-breach-july-2025/
- Revolut CyberSecurity Score History: https://www.rankiteo.com/company/revolut/history
- Revolut CyberSecurity Incident Source: https://thedigitalbanker.com/revoluts-data-breach-shows-institutions-can-be-at-risk-even-when-not-directly-compromised/
- 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