Incident Score: Analysis & Impact (AYA1782455334)
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 AYA Bank'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 AYA Bank 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 AYA Bank breach identified under incident ID AYA1782455334.
The analysis begins with a detailed overview of AYA Bank's information like the linkedin page: https://www.linkedin.com/company/ayabank, the number of followers: 42135, the industry type: Banking and the number of employees: 2015 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 762 and after the incident was 697 with a difference of -65 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 AYA Bank and their customers.
On 25 June 2024, AYA Bank disclosed Data Breach, Extortion issues under the banner "AYA Bank Cyberattack and Data Breach by LAPSUS$".
Myanmar’s AYA Bank confirmed a cyberattack on its digital infrastructure after the extortion group LAPSUS$ claimed to have stolen over 120GB of sensitive data.
The disruption is felt across the environment, affecting Older application portal, and exposing 120GB of sensitive data.
In response, moved swiftly to contain the threat with measures like Strengthened cybersecurity measures, and stakeholders are being briefed through Public statement on Facebook.
The case underscores how Ongoing, with advisories going out to stakeholders covering Internet and mobile banking operations remain unaffected.
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 Exploit Public-Facing Application (T1190) with high confidence (90%), with evidence including older application portal had been breached, and exploitation of older application portal. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with moderate to high confidence (70%), supported by evidence indicating older application portal breached, exposing customer data and Brute Force (T1110) with moderate confidence (50%), supported by evidence indicating lAPSUS$ has history of high-profile cyber-extortion. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), with evidence including 120GB of sensitive data stolen, and personally identifiable customer information. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), with evidence including data exfiltration confirmed, and threat to publish on dark web by July 8 and Exfiltration Over Web Service (T1567) with moderate to high confidence (70%), supported by evidence indicating lAPSUS$ claims to publish data on dark web. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (40%), supported by evidence indicating extortion group LAPSUS$ involved in breach and Defacement (T1491) with lower confidence (30%), supported by evidence indicating public statement on Facebook acknowledging breach. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate confidence (60%), supported by evidence indicating older application portal breached, likely using compromised credentials and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating bank strengthened cybersecurity measures post-breach. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- AYA Bank Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/ayabank/incident/AYA1782455334
- AYA Bank CyberSecurity Rating page: https://www.rankiteo.com/company/ayabank
- AYA Bank Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/aya1782455334-aya-bank-breach-june-2026/
- AYA Bank CyberSecurity Score History: https://www.rankiteo.com/company/ayabank/history
- AYA Bank CyberSecurity Incident Source: https://www.bnionline.net/en/news/myanmars-aya-bank-acknowledges-cyberattack-after-hacking-group-claims-data-breach
- 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