Alert B.V.
bd_64a3f06dc7a9eeaf · schema v1 · pii pii-v2
Full breach record for Alert B.V. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Sovcali on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Alert for lucidmotors. In accordance with our serious intent and our exclusive interest in negotiating solely with the company itself, we have refrained from initiating any discussions with any other company or competitor. To demonstrate that we are in possession of the data in question, we will release an additional 35 gigabytes of material belonging to this company within the next two days.We trust that the company’s officials will reach a definitive decision at the earliest opportunity
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 20, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
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.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.