Cesi
bd_af6d345f3b4b292c · schema v1 · pii pii-v1
Full breach record for Cesi →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage and machine-translated to English — verify against the source.
Summary
machine-translatedCESI victim of a cybersecurity incident - CESI. CESI: CESI was the victim of a cyberattack on Saturday, February 1, 2025, which required cutting off Internet access and mobilizing a crisis cell to contain the incident. Classes were able to resume on Monday, February 3, with continuity measures put in place for students, and the relevant authorities have been notified. The investigation is ongoing to determine the extent of the incident, and the school's management deplores this criminal act. Linked ransomware group: termite.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 1, 2025
Press report
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitetermitebd_6d7491f1387e6e1c2025-02-11 · +10dCandidate
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
termite
According to ransomware.live, Termite is a ransomware group first identified in late 2024 using a modified version of Babuk ransomware code; its most notable attack was the November 2024 breach of supply-chain software firm Blue Yonder, claiming 680 GB of exfiltrated data and disrupting major customers including Starbucks.