← Breach analysis by the Dual Vulnerabilities framework

Kurita America Ransomware (Unattributed, 2024)

2024 · United States · C - Manufacturing · Ransomware attack with data theft

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data theft

Dual vulnerability type

Expertise to Execution

Evidence coverage: 1/6 stages, weight 6/60

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

Why this classification

(1) Kurita America is the North American unit of a Tokyo-listed water-treatment chemicals group, recorded in the dataset as critical infrastructure (chemicals), holding accounting, personnel and ten years of customer water-quality testing data on its servers; the expectation at the victim was that this customer and employee data would stay confidential and that an intruder reading it would be visible to the security monitoring the company demonstrably operated. (2) In practice the ransomware intrusion was handled well on most of the lifecycle - the company's own monitoring raised the alert on 29 November 2024, the compromised servers were disconnected the same day, the main servers were restored without business disruption, and the victim disclosed itself within days and completed an accurate forensics-backed update - but the data stage failed: the actor accessed the stored records and, per the company's own disclosure, the data may have been leaked to third parties, and egress monitoring contributed nothing to stopping or even noticing that; the exposure was bounded only because the encryption alert prompted the disconnection, and five months on the final statement still bounds rather than enumerates what was taken. (3) The expectation that broke originated as material technical capability - egress detection and prevention and forensic reconstruction of what an intruder read, which is specialists' work to implement and tune - and the chain broke in execution: the capability did not deliver in operations. No source documents a strategic directive, an expert warning discounted by leadership, or a deferred investment, so there is no doctrinal-origin or leadership-break evidence; the entry vector was never disclosed and is not load-bearing. The classification rests on the egress stage, the only stage where the documented facts show a victim-side gap; containment, detection, recovery and response are documented as aligned. (4) RM35 (Expertise to Execution lens): sensitive customer, partner and employee data was read and may have been leaked before anything detected it, so the egress visibility that specialists at a monitored critical-infrastructure company should have implemented and tuned around data retained for ten years was not realised in practice, leaving the leak to be bounded by chance disconnection (causal role: Amplifying). RM33 (Expertise to Execution lens): the company could not enumerate what the intruder had taken - scoping took an external forensics firm about five months, the initial 9 December scope of one affected server was superseded, and even the final update speaks only of information the actor may have accessed, leaving the size of the exposure obscured (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Source caveats: the row's second source URL (https://news.kurita-water.com/241207-01) no longer resolves to the article (page now shows a notice that news URLs changed as of 1 October 2025); it was replaced with the opened current article https://www.kurita-water.com/en/news/20241207-01. The April 2025 update is dated 17 April 2025 on the Kurita Water site and 16 April 2025 on the Kurita America site, and its reference line says news release on December 7, 2025 - an evident typo for 2024. Data quality: eurepoc_extra.intelligence_impact states no data breach/exfiltration or leaking of data, contradicting both the row description and the victim's own confirmation that the threat actor accessed the stored data and warning that it may have been leaked; the intelligence_impact field was not used. Attribution: the victim did not name a threat group; 3AM (ThreeAM) is Kaspersky ICS CERT's suspected-attacker entry in its Q4 2024 appendix (primary facts read from the report PDF; the HTML appendix table truncates the attackers column); no leak site was visited (security policy) - leak-site presence is known only as reported in legitimate vendor intelligence and is not load-bearing. The entry vector was never disclosed and is not load-bearing. The egress stage rests on the coder's inference from primary-source facts (no source states a control gap), which sets confidence. No earlier Kurita America incident was found in the sources reviewed, so no recurring-pattern marker is coded. The case file has no related_rows; result-2018.json in the output directory is the separate Ito En North America attack covered by the same The Record article - a different victim and incident, so no alignment is needed. Link check: kurita-water.com was unreachable at check time (timeout); the pages were opened and read during research. Link check: cybersecuritydive.com blocks automated access (HTTP 403); the page was opened and read during research. Sector: the dataset records the receiver as Critical infrastructure / Chemicals and Kaspersky lists it under Chemicals, manufacturing, so the CBS SBI section is C Manufacturing (water-treatment chemicals producer), not E Water supply.