2023 · United Kingdom · C - Manufacturing · Cyber intrusion with unauthorised access to IT systems and data
Analysed 2026-11-07 by Hermes
Open this case in the tool →Cyber intrusion with unauthorised access to IT systems and data
No DV evidenced
Alternative: none defensible
(1) Volex, the AIM-listed British maker of critical power and data transmission products, presented a stated security posture before the incident: established IT security protocols, an incident response plan and business continuity principles subject to regular testing, with cybersecurity already identified as a high risk in its risk register (Notice of Cyber Incident, 9 October 2023; Annual Report and Accounts 2024). (2) In October 2023 an unattributed actor gained unauthorised access to certain IT systems and data at some of the Group's international sites; Volex enacted its protocols, engaged specialist third-party consultants, implemented the incident response plan, kept all 27 manufacturing sites operational with functional impact under a day, self-disclosed to the market on 9 October with updates on 24 October and 23 November, and booked $2.0m of recovery and remediation costs as an exceptional item. (3) Research across all six lifecycle stages (victim RNS announcements and Annual Report 2024, The Register, SecurityWeek, The Record, teiss, plus searches for attribution, ransomware claims, regulator action and follow-up reporting) yields no victim-side failure mechanism anywhere: the entry vector, dwell time, detection route and root cause were never disclosed despite the consultant investigation, no regulator or formal investigation examined the controls, and EuRepoC records no confirmed data exfiltration and no material disruption. The response, recovery and disclosure conduct is documented as aligned, but because the intrusion succeeded at some sites for undocumented reasons, alignment across the lifecycle is not confirmed either, so neither a DV-Type nor No DV evidenced can be defended; reporting confirms impact only, which is the method's decision rule for Unknown. The entry vector is unknown and not load-bearing for any classification.
All incident evidence is one-sided: the victim's own disclosures (RNS 9/24 October and 23 November 2023, Annual Report and Accounts 2024); press coverage adds no mechanism and Volex did not answer follow-up questions on entry vector, dwell time, ransom or malware. EuRepoC records no confirmed data breach/exfiltration and functional impact under a day, while the disclosures confirm unauthorised access to certain IT systems and data - recorded as reported by each source. SecurityWeek's suggestion of an early-discovered or non-encrypting ransomware attack is speculation, not evidence; no ransomware group listed Volex. Post-incident changes (new Group CIO to lead IT and cybersecurity strategies, additional mitigations, expanded mandatory e-learning - AR2024) are noted but do not evidence a documented pre-breach gap. No regulator, court or parliamentary follow-up found; no related_rows in the case file and no other Volex rows in the 500-row run. The case file description matches the stated victim; no data-quality issue.