← Breach analysis by the Dual Vulnerabilities framework

Finastra Data Breach (abyss0, 2024)

2024 · United States · K - Financial and insurance activities · Data theft via compromised credentials on a file transfer platform

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Data theft via compromised credentials on a file transfer platform

Dual vulnerability type

Expertise to Execution

Evidence coverage: 3/6 stages, weight 22/60

Decisive stage: detection (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) Finastra is a critical-infra finance vendor that operates a SOC and moves large volumes of banking-related files for roughly 8,100 financial institutions, and it maintains a designated default file-exchange platform - the expectation was credential-protected access to its customer-data transfer systems and detection of bulk exfiltration by its own monitoring. (2) In practice, a criminal using the alias abyss0 logged in with compromised credentials to an internally hosted, non-default SFTP used to send customers technical and support files, obtained files on 31 October 2024 and offered the data for sale that same day; Finastra's SOC detected suspicious activity only on 7 November, when the intruder returned, its customer notice shows it learned of the exfiltration from the attacker's dark-web claim, and its own letter had to assess which of its products were not dependent on the specific version of the SFTP platform that was compromised - scope that took until 12 February 2025 to resolve to a small number of individuals (names plus financial account information). (3) The failed expectations sit in the material column: credential protection, SOC detection and egress monitoring are known technical remedies that Finastra demonstrably runs elsewhere, but none functioned on this legacy internally hosted platform - the classification rests on the detection stage (clearest evidence: the victim's own notification-letter timeline plus Krebs' reporting of the pre-detection sale), the break is execution because no source shows leadership deferring or lacking these controls, and the entry vector (compromised credentials, per Finastra's own root-cause statement) is documented but secondary. (4) RM22 (Expertise to Execution lens): on this internally hosted, non-default SFTP ordinary credentials were sufficient to log in and pull files, and the victim's own root-cause statement - compromised credentials whose source was never identified, even in the February 2025 letter - shows MFA, lifecycle or leaked-credential controls were not realized on the platform (causal role: Enabling). RM34 (Expertise to Execution lens): the SOC and its tooling existed and worked when it finally triaged the case, but they were evidently not tuned to flag anomalous legitimate access, since the 31 October retrieval passed unnoticed and the incident surfaced only because the attacker came back a week later (causal role: Obscuring). RM35 (Expertise to Execution lens): a bulk retrieval the attacker claimed at 400 GB left the platform undetected and uninterrupted, and the first signal of exfiltration was the attacker's forum post, so outbound monitoring on the very platform built to move large files out did not function (causal role: Amplifying). RM15 (Expertise to Execution lens): Finastra's eDiscovery revealed a visibility gap in its own estate - it had to work out which products were not dependent on the compromised version of the internally hosted SFTP, and mapping affected customers took months, showing the platform and the data flowing through it were not clearly inventoried or classified (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

Country taken from eurepoc_extra.receiver_country (United States) per the EuRepoC procedure; Finastra is London-headquartered (Krebs), but the individual notifications ran through the US entity Finastra Technology Inc (Massachusetts OCABR filing). The 400 GB figure is the attacker's unverified claim - the BreachForums post and Telegram account were later deleted - and Finastra only ever confirmed that certain files were obtained; the scale claim rests on secondary reporting (KELA screenshots) and is not load-bearing for the classification. The row's data_theft field ('non-sensitive information, 1 point') understates the notification letter's content (names plus financial account information, with 24 months of credit monitoring offered). Earlier incident: a March 2020 ransomware attack (Krebs, BleepingComputer); the vulnerability-management findings reported around that incident concern a different vector and no source links them to the 2024 credential compromise, so RM21 was not coded. SecurityWeek (18-02-2025) speculated that the deleted forum post suggested negotiations or a payment to delete the data - speculation, not adopted. No regulator, court or formal investigation findings were located. The Check Point threat-intelligence report listed in source_url was not opened and is not cited. Link check: mass.gov blocks automated access (HTTP 403); the page was opened and read during research (the notification-letter PDF was downloaded in full and read). The CSO Online German article from the row's source_url returned 410 at link-check time; it was read during research via article extraction but is not cited; its facts are corroborated by KrebsOnSecurity, BleepingComputer and SecurityWeek.