Loxone GmbH
bd_94e929bbdbd36031 · schema v1 · pii pii-v2
Full breach record for Loxone GmbH →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-translatedSecurity incident at Loxone (Oct 18, 2026). Loxone: Loxone, an Austrian building automation technology company, confirmed it was the victim of a cyberattack on its internal systems on October 18, 2026. The attack appears to be ransomware-related, with threats to publish exfiltrated data (approximately 201.6 GB). Although the core automation systems (Miniserver, Remote Connect) do not appear to be affected, the group is working with cybersecurity experts to isolate compromised systems and conduct a forensic analysis.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 18, 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.