WIBAIE
bd_a47aabe63dba3b2e · schema v1 · pii pii-v1
Full breach record for WIBAIE →2 incidents on filePress / 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-translatedA cyberattack paralyzes this large company in Maine-et-Loire: the factory is shut down. Wibaie: The Wibaie company in Cholet suffered a cyberattack during the night of July 9 to 10, 2025, which resulted in a complete shutdown of the factory. The company, which is part of the Liébot Group, is working with experts to resolve the issue. Approximately 600 employees are currently immobilized due to this cyberattack.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 10, 2025
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
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.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
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.