← Breach analysis by the Dual Vulnerabilities framework

Lagoon Ransomware Attack (Unattributed, 2024)

2024 · New Caledonia · J - Information and communication · Ransomware attack with data-theft extortion

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with data-theft extortion

Dual vulnerability type

Expertise to Execution

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

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

Why this classification

(1) As a New Caledonian ISP and hosting provider whose network serves subscribers, businesses and hosted public-linked sites, Lagoon was expected to keep its perimeter remediated, its logs retained and protected, and a scoping capability ready; the company itself later took NIS-2 as the benchmark for what it should have had. (2) In practice, a Crypto-type ransomware was launched at 03:30 on 18 August 2024; the company's own post-incident analysis concluded the intrusion was facilitated by a flaw in a firewall; the malware encrypted the hosting platform, taking email down for two weeks, about 40% of subscribers offline for around 48 hours and hosted business servers for up to three weeks; the attackers erased four months of server logs and left a backdoor, so the company long could not say whether personal data had been taken, and only an internal-document leak was ever confirmed. The company detected the attack within about 4.5 hours, isolated systems within minutes, restored all services without paying by 19 September, and disclosed next day. (3) The classification rests on the entry stage, the only stage whose origin and break are documented by a source: the expectation sat with technical specialists (a firewall flaw is a known, remediable state, and the case file records no zero-day), and the chain broke in execution, the remedy never realised before the flaw was exploited. The doctrinal gap at the response stage - a complete cyber strategy, hosting investment and NIS-2 compliance announced only after the breach - is a secondary Strategy-to-Leadership pattern but rests on inference and cannot outrank the documented entry gap. The exact entry vector was never publicly named beyond the firewall flaw, and attribution remained unresolved. RM18 (Expertise to Execution lens): the firewall flaw identified by the company's own analysis was known and remediable rather than a zero-day, but remediation lagged the operational reality and the attackers exploited it to get in (causal role: Enabling). RM33 (Expertise to Execution lens): experts could not investigate because log retention was not protected - the hackers erased four months of server logs, leaving no forensic trace, and the scope of compromised data stayed undetermined for weeks (causal role: Obscuring). RM35 (Expertise to Execution lens): data left without being detected or interrupted - the ransom demand hinged on claimed exfiltration, and the company, which had no egress picture to fall back on, could confirm only an internal-document leak (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; victim, country and year taken from the case file (receiver_country New Caledonia, start_date 18.08.2024). Dataset inconsistency: eurepoc_extra.intelligence_impact says 'No data breach/exfiltration ... or leaking of data', while the row description and the victim's own later statements confirm the ransom demand was based on taken data and an internal-document leak was confirmed. The firewall flaw comes from the company's analysis as reported by one local outlet with hedged wording ('aurait ete facilitee'); no CVE was ever publicly named (Zataz only hypothesised CVE-2024-21762 - speculation, not used); it is read as a remediable flaw rather than a misconfiguration ('faille'), so RM18 rather than RM27. Lagoon reports having countered two earlier cyberattacks (before and during the Covid period) - too undocumented to code a recurring-weakness marker. The May 2024 unrest had already put the company's Plexus backup centre in Ducos out of service and weakened it, but no source links that loss to the recovery time, so it is described here and not coded. Ransom amount and whether it was paid were never disclosed; contact with the attackers was handled by the police (ComCyberGend). ANSSI, DINUM, the Centre Cyber du Pacifique and a local audit firm supported the response. Facebook post in source_url not opened (login wall); zataz, la1ere and neotech carry the same facts.