2020 · United Kingdom · K - Financial and insurance activities · Ransomware attack with data theft and multi-week global service outage
Analysed 2026-11-07 by Hermes
Open this case in the tool →Ransomware attack with data theft and multi-week global service outage
Strategy to Leadership
Evidence coverage: 3/6 stages, weight 19/60
Decisive stage: response (tie-break: post-breach stage) · Alternative: Expertise to Execution
(1) The strategic expectation at Travelex, a regulated foreign-exchange business in the LSE-listed Finablr group, was to remediate a critical, publicly warned VPN vulnerability and, in an incident, to notify the ICO within 72 hours and communicate accurately to the market and its customers. (2) In practice, attackers deployed Sodinokibi ransomware on New Year's Eve 2019 through Pulse Secure VPN servers that had stayed unpatched for about eight months despite a vendor patch (April 2019), public exploits and a direct September 2019 warning naming seven exposed servers. Once inside, the attackers encrypted the network and claimed to have copied about 5GB of customer data, while the company could not scope what had been taken; the public narrative ran from planned-maintenance notices to a software virus to repeated assertions that there was no evidence any data had been exfiltrated (market announcement 8 January, CEO video 17 January), the ICO confirmed on 8 January that nothing had been reported to it within the 72-hour window, and the ransom payment of roughly $2.3 million the company had made was only revealed by Wall Street Journal reporting in April 2020. (3) The classification rests on the response/disclosure stage: the expectation was doctrinal (legal notification duties, listed-company disclosure obligations, the company's own public commitments), and the chain broke at the decision level - what was notified, what was denied publicly while negotiations ran, and what was concealed (the payment). That is a gap within the doctrinal column, i.e. a public narrative contradicted by the organisation's own later-documented conduct, which is the Strategy to Leadership pattern; it is not IT failing to execute a decided policy. The entry gap is a real second pattern - a known remedy available and warned against but not executed (Expertise to Execution) - and it is load-bearing, but the equally well-documented response stage sits further from the breach moment, so the post-breach tie-break makes response decisive; the entry vector itself is corroborated only by secondary reporting and is not what the DV-Type rests on. RM18 (Strategy to Leadership lens): leadership priorities and risk tolerance allowed a known VPN exposure to persist against remediation expectations - the CVE-2019-11510 patch dated back to April 2019 and warnings ran through October 2019, yet the servers were still exploitable at year-end (causal role: Enabling). RM19 (Strategy to Leadership lens): the external warning of 13 September 2019 that specifically named seven vulnerable internet-facing Pulse Secure servers received no response, showing no leadership process gave that warning ownership or oversight before the breach (causal role: Enabling). RM35 (Strategy to Leadership lens): exfiltration and data-loss risk received no strategic attention in practice - bulk customer data was reported stolen while the company could not detect or bound the outflow and insisted no data had left (causal role: Amplifying). RM39 (Strategy to Leadership lens): disclosure behaviour diverged from legal expectations and the company's own commitments - no ICO notification within 72 hours, public denial of exfiltration during ransom negotiations, and a ransom payment kept undisclosed until leaked reporting forced it out (causal role: Constraining).
RM18 — Vulnerability / patch latencyRM19 — Vulnerability disclosure handling gapRM35 — Egress / exfiltration monitoring gapRM39 — Breach notification / disclosure failureCase file is a cyberdefensemagazine row whose description holds two article titles; both match Travelex (the Wired piece is primarily about 2021 Pulse Secure VPN espionage and is cited as context for VPN exposure and the Travelex entry vector). Entry vector: reporting (Ars Technica, WSJ as cited in Wired/Dark Reading, CyberInt) attributes initial access to unpatched Pulse Secure VPN (CVE-2019-11510); the victim never published forensic confirmation, and some coverage also mentioned Fortinet flaws - the vector is treated as corroborated secondary evidence and is not load-bearing for the DV-Type. The six-month dwell time and 5GB exfiltration figures are attacker claims, cited only as reported by mainstream press and never independently confirmed in the opened sources. The ransom payment is reported by the Wall Street Journal via a person familiar with the transaction; Travelex never confirmed it. No ICO fine against Travelex appears in the opened record, and the full scale of customer notification could not be confirmed in opened sources - both left out of the claims rather than guessed. Attack onset was 31 December 2019 (discovery 31 Dec/1 Jan); Year recorded as 2020, the year of the disruption and disclosure events; Finablr disclosed about GBP 25m of incident cost. Link check: shareprices.com blocks automated access (HTTP 403); the page was opened and read during research.