← Breach analysis by the Dual Vulnerabilities framework

Vesuvius Cyber Incident (Unattributed, 2023)

2023 · United Kingdom · C - Manufacturing · Cyber attack forcing a precautionary group-wide IT shutdown (suspected ransomware)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Cyber attack forcing a precautionary group-wide IT shutdown (suspected ransomware)

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) Vesuvius plc, an LSE-listed, FTSE 250 manufacturer of molten metal flow engineering products for the steel and foundry industries (a critical-manufacturing supplier), maintained a formal cyber-risk programme: the 2023 annual report describes cyber as a component of its business-interruption principal risk, integrated with its Business Continuity Plan and Disaster Recovery Plan, with penetration testing, awareness training and board-level reporting, and credits protective measures implemented in prior years. (2) What is documented of the incident itself is impact and response conduct only: unauthorised access was discovered by the company itself, it shut its systems on a precautionary basis, sites ran their business continuity plans, forensics firms were engaged, the market was informed the same day via an RNS inside-information announcement (6 February 2023), the incident cost c. £3.5m as a one-off, the company states it fully recovered within months with no disruption of supply to customers, and the annual report reports lessons learned and funded follow-up measures (accelerated cyber security strategy, upgraded third-party access solutions, network infrastructure work, added protection layers). A month after the disclosure, the Vice Society ransomware gang claimed the attack and published files it said were stolen from Vesuvius on its leak site; the victim never confirmed this, nor ever disclosed the entry vector, the nature of the attack, the dwell time or whether data was taken. (3) Because the only primary sources are the victim's own deliberately minimal disclosures, and no regulator, court or forensic report examines a victim-side failure, no concrete failure point can be placed on either DV axis: reporting confirms impact (a precautionary worldwide IT shutdown, £3.5m cost, claimed data leak) but the cause of exposure is undetermined in the record. The victim's alignment claims are self-assessments written after the event and the intrusion itself did occur, so the positive-evidence bar for No DV evidenced is not met either; the decision rule for Unknown (impact confirmed, no defensible victim-side mechanism at any stage) applies. The precautionary group-wide shutdown is noted in Notes as the only candidate structural condition, but no source characterises it as a concentration weakness, so it is described here rather than coded.

Sources

Notes

Unknown per the decision rule: reporting confirms impact only; the entry vector, attack nature, detection time and dwell time were never disclosed and no regulator or forensic report is public. The data-theft claim (files published ~1 March 2023) rests on the attacker's unverified leak-site claim as reported by legitimate press; Vesuvius never confirmed it and no leak site was accessed for this analysis. Dataset consistency: the row codes has_disruption=False and functional_impact 'No system interference/disruption' while its description says the company was required to temporarily shut down operations; the company's own 2023 annual report describes a precautionary systems shutdown with only minimal business interruption and no disruption of supply to customers, so the row coding is defensible on supply impact though not on IT impact. The dataset's London Stock Exchange source_url could not be read (bot-blocked); the identical RNS text was read at the Euroland mirror cited in Manual source-article. Economic impact in the row (USD 4.6m) matches the company's stated c. £3.5m one-off cost. Link check: databreaches.net blocks automated access (HTTP 403); the page was opened and read during research. Link check: vesuvius.com blocks automated access (HTTP 403); the page was opened and read during research (the interim results transcript PDF was downloaded and read with pdftotext).