Batipro
bd_fd8c30e845ce4e56 · schema v1 · pii pii-v2
Full breach record for Batipro →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 — verify against the source.
First known cyberattack on construction sector delays overtime pay for 800 staff. Batipro: Batipro, a building materials supplier based in Betrange, was the victim of a cyberattack that targeted all six of its servers. The incident, which occurred over the weekend, could potentially result in a slight delay in the payment of overtime. The LCGB union notes that this is the first case of a cyberattack in the construction sector in Luxembourg, highlighting a perceived increase in such incidents. The article also mentions other recent incidents, such as attacks on medical practices and government websites.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 6, 2026
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.