← Breach analysis by the Dual Vulnerabilities framework

Cooler Master Fanzone data theft (Ghostr, 2024)

2024 · Taiwan · C - Manufacturing · Data theft via compromised customer-facing web portal

Analysed 2026-11-07 by Hermes

Open this case in the tool →

What happened

Data theft via compromised customer-facing web portal

Dual vulnerability type

Expertise to Execution

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

Decisive stage: containment (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) The expectation at the victim: a hardware manufacturer running a customer-facing warranty/RMA/loyalty portal that collects names, birth dates and addresses was expected to hold its customer portal apart from internal databases by a real trust boundary, and to keep customer records classified apart from employee, vendor and corporate data. (2) In practice, around 18-19 May 2024 the actor 'Ghostr' breached one of Cooler Master's front-facing websites and downloaded numerous linked databases: CSVs appearing exported from the Fanzone portal held customer, employee, vendor and product data (about 1,000 RMA records verified by BleepingComputer), and the company's own notice confirms names, postal addresses, phone numbers, emails and credit card numbers were acquired. The company says its measures alerted it on 19 May and it engaged forensic experts and later offered credit monitoring; it never disclosed the entry vector, the number of victims, or the volume exfiltrated. (3) The classification rests on the containment stage: the unmet remedy - isolating a public web frontend from its linked databases - sits with technical specialists (material origin), and no source shows a decided-and-resourced separation that operations failed to deliver, so the break is execution: the known architecture practice simply was not realized, producing a one-intrusion blast radius across customer, employee and vendor data. The entry vector is undisclosed and not load-bearing (Ghostr's later-attributed SQL injection/RDP pattern is context only). The egress gap (bulk export neither stopped nor ever sized publicly) is the same material/execution pattern; the competing response-stage reading sits in the Alternative DV-Type. RM30 (Expertise to Execution lens): specialists could not realize containment for this portal - a single compromise of the customer-facing site reached numerous linked internal databases, making the blast radius disproportionate to one web intrusion, as the verified multi-domain CSV exports show (causal role: Amplifying). RM35 (Expertise to Execution lens): bulk data left through the web frontend without egress monitoring able to stop or interrupt it, and the architecture left the company unable to state the exfiltration volume even in its own notice letter (causal role: Amplifying). RM16 (Expertise to Execution lens): the verified Fanzone exports mixing customer, employee, vendor and product records show data ownership, inventories and classification were not operationalized around the portal, so more and more sensitive data was exposed than a warranty-registration site needed (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

The 103 GB and 500,000-customer figures are the attacker's unverified claims; BleepingComputer verified only ~1,000 RMA/support records in a sample and found no credit-card data there, and heise reported that how the attack actually took place remained unclarified and Cooler Master had not said how many customers were affected. The company's claim that its own measures alerted it on 19 May comes from its own notice letter (primary but self-serving); Ghostr's claim that he first contacted the company with a payment demand and got no response is unverified attacker statement. Cooler Master's special-announcement page now returns an HTTP error and is not cited; its existence and date are taken from the contemporaneous coverage. Link check: mass.gov blocks automated access (HTTP 403); the page was opened and read during research (downloaded as a PDF and read with pdftotext). Related row 2105 (EuRepoC) carries the same Ghostr/103 GB incident per its title, but no row-2105.json case file exists in cases-run500 and no result-2105.json exists in the output directory, so it could not be read or aligned. The case file gives no year; Year 2024 and Country Taiwan (headquarters; the Massachusetts notice was filed by the US subsidiary Cooler Master Technology Inc., Providence RI) come from the sources above. The actor's identity, multi-alias history and arrest (Feb 2025, joint Singapore-Thailand operation) are post-incident context only and not part of the DV evidence.