CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Die Linke ransomware breach

incident · incident:die-linke-qilin-2026

Suspected Qilin ransomware attack on the German party Die Linke, disclosed 2026-03-27; Qilin listed the party on its leak site on 2026-04-01.

Coverage
1
first 2026-05-08 → last 2026-09-30
Latest activity
2026-05-08
Die Linke took parts of its IT infrastructure offline after a suspected Qilin attack; Qilin listed it without…
Peak priority
routine
1 routine
Targets
·
regions: europe, dach
Sources cited
4
4 hosts

Story timeline

  1. 2026-05-08Qilin claims a ransomware attack on the German party Die Linke; the party has not confirmed data theft
    active-threatsDie Linke took parts of its IT infrastructure offline after a suspected Qilin attack; Qilin listed it without samples

Hunting pivots

ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.0 · compare on the matrix · Navigator layer (JSON)

  • ImpactData Encrypted for Impact

Impact TA0040

T1486Data Encrypted for Impact×1

Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.

Evidence: 2026-05-08/qilin-ransomware-hits-die-linke-germany-1-5-tb-claimed-dpa-n · ATT&CK page ↗

Entries about Die Linke ransomware breach (1)

2026-05-08 · view entry permalink →

ROUTINEupdatedNATOB2

Qilin claims a ransomware attack on the German party Die Linke; the party has not confirmed data theft

Die Linke detected a cyberattack on its IT network on Thursday, 26 March 2026, took parts of its IT infrastructure offline as a precaution and filed a criminal complaint. In a statement the next day it said it had indications of a ransomware attack by the Qilin group and that its member database was not affected (Die Linke, 2026-03-27). Heise reported that it had not yet been definitively clarified which internal data had been compromised (Heise Online, 2026-03-27). Qilin added the party to its leak site on 2026-04-01 without publishing data samples (BleepingComputer, 2026-04-03). Contradiction: BleepingComputer's headline says the party confirmed the data theft, while its own text says the party stopped short of confirming a data breach (BleepingComputer, 2026-04-03). The party says the attackers aim to publish sensitive internal data and personal information of headquarters staff, and that it cannot assess whether or to what extent this will succeed or has already happened (Die Linke, 2026-03-27).

The sources give no access vector, so the transferable ground is the target class: German political parties have been targeted by cyberattacks before (The Record, 2026-04-06), and Die Linke describes ransomware attacks as often part of hybrid warfare and this one as aimed at weakening democratic structures (Die Linke, 2026-03-27).

it has not yet been definitively clarified which internal data has been compromised

Heise Online 2026-03-27
Correctionrun 2026-09-30T0639Z-audittitleheadlinesummaryevent_dateprioritytechniquessourcesevidenceverificationclassificationbodysourcing_noteconfidence

The earlier text said the party confirmed in April 2026 that its data was encrypted and exfiltrated, that Qilin claimed 1.5 TB, and that the state data protection authority was notified. Die Linke disclosed the attack on 2026-03-27 (Heise Online, 2026-03-27), Qilin listed it on 2026-04-01 without samples (BleepingComputer, 2026-04-03), Heise reported that which internal data was compromised had not yet been definitively clarified (Heise Online, 2026-03-27), and the party says it cannot assess whether the attackers' aim of publishing internal data will succeed or has already occurred (Die Linke, 2026-03-27). The 1.5 TB and notification claims appear in no reachable source and are removed.

incident08 May 05:00Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats1

Source distribution

  • bleepingcomputer.com1 (25%)
  • die-linke.de1 (25%)
  • heise.de1 (25%)
  • therecord.media1 (25%)