← Breach analysis by the Dual Vulnerabilities framework

Albany ENT & Allergy Services ransomware and data leak (RansomHouse and BianLian, 2023)

2023 · United States · Q - Human health and social work activities · Ransomware attack with data theft and leak (two threat actors)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data theft and leak (two threat actors)

Dual vulnerability type

Strategy to Leadership

Evidence coverage: 5/6 stages, weight 41/60

Decisive stage: response (tie-break: post-breach stage) · Alternative: Strategy to Execution

Why this classification

(1) Strategic expectation: as a HIPAA covered entity and under New York GBL 899-aa/899-bb, AENT was held to legal duties to secure patient data and to notify regulators and 224,486 affected individuals accurately and completely; it also held its own security artefacts (an MFA requirement and a laptop-scoped encryption policy). (2) In practice: two ransomware actors infiltrated between 23 March and 4 April 2023; the IT vendor restored systems after the first detected event without identifying the source and reconnected external access, letting a second actor in on 2 April; PI sat unencrypted on six devices; and the 25 May notification described only 'suspicious activity', omitting ransomware, the two groups, the exfiltration and the ongoing dark-web leak, while under-scoping the exposed data - the NY Attorney General found driver license numbers in the attackers' posted files and AENT corrected its notice only after being confronted, then violated GBL 899-aa and 349. (3) The classification rests on the response/disclosure stage: the unmet expectation was doctrinal (a statutory notification duty plus the organisation's own disclosure obligations, found breached by the regulator) and the chain broke at leadership, which chose and signed an inaccurate, incomplete public narrative while the attackers' own leak said otherwise - espoused commitment diverging from enacted leadership communication, the Strategy to Leadership pattern. The entry vector itself is only 'likely' (forensic conclusion via the NY AG) and is not load-bearing; the entry and egress gaps (MFA and encryption artefacts never operationalised) are a secondary Strategy to Execution pattern that carries the largest share, and the documented re-infection an Expertise to Execution pattern; under the tie-break the post-breach response stage decides. (4) RM39 (Strategy to Leadership lens): leadership disclosure behaviour diverged from legal expectations - the notification concealed ransomware, the second actor and the leak, and its figures were corrected only under regulator pressure, leaving 224,486 patients uninformed that their data was already published (causal role: Constraining). RM38 (Strategy to Leadership lens): the pressure to restore service beat full eradication - the vendor restored and reconnected external access before the breach source was identified, so access returned six days later (causal role: Amplifying). RM22 (Strategy to Leadership lens): leadership never required an authentication model consistent with the risk - its own MFA requirement was never adopted on certain remote-access systems, the path through which the actors likely entered (causal role: Enabling). RM26 (Strategy to Leadership lens): leadership did not require data protection commensurate with sensitivity - the encryption policy stopped at laptops while six devices hosted unencrypted PHI, some unremediated for months after the breach (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: maine.gov blocks automated access (HTTP 403); the page was opened and read during research. Source caveats: the rackcdn notification-PDF URL in the case file returns 404; the notification text was read as quoted by DataBreaches and InformationSecurityMedia and via the Maine AG filing page and a Massachusetts AG copy found in search (the Massachusetts copy itself was not separately opened and is not cited). The Maine AG record lists discovery 02 May 2023 while the notification letter describes awareness of suspicious activity on 27 March - the NY AG findings resolve this: first infiltration discovered 27 March, second on 2 April, forensic review concluded 2 May (data-quality note, not a contradiction in the incident itself). EuRepoC classifies the stolen data as non-sensitive (intensity 1 point); the NY AG Assurance shows SSNs, driver-license numbers and treatment data exfiltrated, so that field understates impact. Volumes 630 GB (BianLian) and 2 TB (RansomHouse) are attacker claims reported via DataBreaches/teiss, not victim-confirmed; the NY AG confirms only that exfiltration evidence was provided and both actors posted files. The ransom non-payment was a governed, documented decision following the OFAC advisory (AOD para 6), so RM42's exclusion condition applies and it is not coded. Notification reached regulators within statutory deadlines; the disclosure failure is about content (concealment/inaccuracy), not timing. Settlement: NY AG Assurance No. 24-016, USD 1M penalty (USD 500k suspended) plus USD 2.25M security investment over five years; no public HHS OCR enforcement reported as of the DataBreaches settlement article (30 Oct 2024).