← Breach analysis by the Dual Vulnerabilities framework

ThyssenKrupp Failed ransomware attack (Unattributed, 2024)

2024 · Germany · C - Manufacturing · Failed ransomware attack with precautionary IT shutdown

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Failed ransomware attack with precautionary IT shutdown

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) ThyssenKrupp is a German industrial conglomerate classified in the dataset as critical infrastructure (critical manufacturing); the expectation for its automotive body production unit would be perimeter integrity, detection and isolation capability, but the record names no strategic artefact (policy, programme, standard) at all, so the doctrinal side cannot be evidenced. (2) Operationally, an unidentified attacker gained unauthorised access to the IT infrastructure of the Automotive Body Solutions business unit; the company said the IT security team of the unit 'recognized the incident at an early stage' and that it contained the threat together with the group's IT security team by taking certain applications and systems temporarily offline, which halted car body production at several plants (including Wadern-Lockweiler in Saarland, about 1,000 employees) for 1 to 7 days; the company confirmed to SecurityWeek that 'it was a ransomware attempt which failed', reported no data theft or manipulation and no impact on other business units, and worked on a phased return to normal operations. (3) The classification is Unknown because no lifecycle stage yields a defensible victim-side mechanism: the entry vector is undisclosed (the company itself told Golem.de that when the attack happened, who was responsible and through which weaknesses initial access occurred were all still unclear, and BleepingComputer reported no actor had claimed it, so the type of breach remained unknown), no forensic investigation, regulator finding or follow-up reporting was published, and the only evidence pointing the other way - early own-detection, successful containment, failed encryption, no exfiltration, same-day confirmation to the press - rests solely on the victim's own brief statements, which the method requires to be treated as unverified; that is not enough to certify a confirmed negative either, so neither a DV-Type nor 'No DV evidenced' can be defended. The precautionary shutdown halting multi-plant production is a documented dependency condition but no source explains the underlying architecture, so it is described here rather than coded. Context only: ThyssenKrupp units were repeatedly breached before (2013 espionage, 2016 trade-secret theft attributed to Southeast Asia, 2020 NetWalker ransomware against the North-American Materials unit, 2020 Mount Locker against System Engineering, 2021 subsidiary ransomware, December 2022 attack on Materials Services and headquarters); with no root cause disclosed for any of them, no recurring comparable weakness can be established.

Sources

Notes

Row description matches the stated victim (ThyssenKrupp, Automotive Body Solutions, Saarland plant) - no data-quality mismatch. The EuRepoC row codes disruption >24h, functional impact <7 days, no data breach/exfiltration and zero economic impact; reporting corroborates availability loss only. The incident record beyond impact consists of the victim's own PR statements; primary reporting (Golem.de, BleepingComputer) explicitly states the attack path, timing and attribution were unknown, and no later attribution, forensic report, regulator action or leak-site claim surfaced in legitimate reporting up to November 2026; the Saarbruecker Zeitung first report is paywalled. 'No DV evidenced' was considered and rejected: the positive-evidence-of-alignment requirement is not met by self-reported containment success with the intrusion path itself unexplained. Related row 2550 (perennial Winnti/WickedPanda espionage campaign against various German companies) is listed in the case file, but its case file is not among the 500 case files in this run and no result exists for it, so no connection to this incident can be stated. Earlier ThyssenKrupp incidents (2013, 2016, 2020, 2021, 2022) are recorded in the rationale as context; without disclosed root causes, RM21 was not coded. Kaspersky ICS CERT (Q1 2024 overview) lists the incident as denial of IT systems / denial of operations and notes such reports rest on the victim companies' own statements. Unattended run: no step required consent (no forms, uploads or posts).