ABECOM LTDA
bd_e63c007fd4dc304e · schema v1 · pii pii-v1
Full breach record for ABECOM LTDA →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Knight 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
We have more than 170 GB of confidential ABECOM company files, contracts, finances, projects, customer and employee data, reports, sales and purchase documents, returns, freight, invoices, photos of employees' cars, photos of employees, vehicle checks, repair and warranty submissions, thermography, signatures, photos and videos.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 29, 2024
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.
knight
According to ransomware.live, [Cyclops](group/cyclops) rebrand