Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Bank3 » BAN1776364185

Incident Score: Analysis & Impact (BAN1776364185)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-121
Company Score Before Incident753 / 1000
Company Score After Incident632 / 1000
Company LinkView Bank3 Profile
INCIDENT NUMBERBAN1776364185
Type of Cyber IncidentRansomware
ATTACK VECTORNA
DATA EXPOSED149 GB of data
INCIDENT DATE24/07/2025
STATUSOngoing

Key Highlights From The Incident Analysis

  • Timeline of Bank3's Ransomware 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 Bank3 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 Bank3 breach identified under incident ID BAN1776364185.

The analysis begins with a detailed overview of Bank3's information like the linkedin page: https://www.linkedin.com/company/bank3memphis, the number of followers: 785, the industry type: Banking and the number of employees: 46 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 753 and after the incident was 632 with a difference of -121 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 Bank3 and their customers.

On 13 October 2025, Bank3 disclosed Data Breach, Ransomware issues under the banner "Bank3 Data Breach Exposes Sensitive Customer Information in 2025 Cyberattack".

Bank3, a regional commercial bank, experienced a cybersecurity incident where an unauthorized actor accessed its systems between July 25 and August 7, 2025, viewing or exfiltrating sensitive data.

The disruption is felt across the environment, and exposing 149 GB of data.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Secured systems immediately upon detection, and stakeholders are being briefed through Written notice to affected individuals on April 15, 2026.

The case underscores how Ongoing, with advisories going out to stakeholders covering Written notice sent to affected individuals on April 15, 2026.

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 moderate confidence (50%), supported by evidence indicating unauthorized actor accessed the bank’s systems between July 25 and August 7 and Valid Accounts (T1078) with moderate confidence (60%), supported by evidence indicating suspicious activity on its network detected on August 20, 2025. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with lower confidence (40%), supported by evidence indicating ransomware group Qilin claimed responsibility for the breach. Under the Credential Access tactic, the analysis identified OS Credential Dumping (T1003) with moderate to high confidence (70%), supported by evidence indicating social Security numbers, driver’s license numbers compromised and Unsecured Credentials: Credentials In Files (T1552.001) with moderate confidence (60%), supported by evidence indicating financial account and payment card details exposed. Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate to high confidence (70%), supported by evidence indicating personal and financial information for all clients compromised and File and Directory Discovery (T1083) with moderate confidence (60%), supported by evidence indicating 149 GB of data allegedly stolen by Qilin. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating names, SSNs, DOBs, financial details, health insurance info compromised and Data Staged: Local Data Staging (T1074.001) with moderate to high confidence (70%), supported by evidence indicating 149 GB of data exfiltrated by Qilin. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating qilin posted details on the dark web, alleging 149 GB stolen and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate confidence (50%), supported by evidence indicating data exfiltration confirmed by third-party forensic specialists. Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (40%), supported by evidence indicating incident type listed as ransomware and Data Destruction (T1485) with lower confidence (30%), supported by evidence indicating attack threatening the organizations existence. Under the Defense Evasion tactic, the analysis identified Indicator Removal: Clear Windows Event Logs (T1070.001) with moderate confidence (50%), supported by evidence indicating unauthorized access undetected for 13 days (July 25-August 7) and Impair Defenses: Disable or Modify Tools (T1562.001) with lower confidence (40%), supported by evidence indicating suspicious activity detected only on August 20, 2025. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (50%)
Valid Accounts (60%)
Execution
User Execution: Malicious File (40%)
Credential Access
OS Credential Dumping (70%)
Unsecured Credentials: Credentials In Files (60%)
Discovery
Account Discovery (70%)
File and Directory Discovery (60%)
Collection
Data from Local System (80%)
Data Staged: Local Data Staging (70%)
Exfiltration
Exfiltration Over C2 Channel (90%)
Exfiltration Over Web Service: Exfiltration to Cloud Storage (50%)
Impact
Data Encrypted for Impact (40%)
Data Destruction (30%)
Defense Evasion
Indicator Removal: Clear Windows Event Logs (50%)
Impair Defenses: Disable or Modify Tools (40%)

Sources & References