Arban & Carosi
bd_800dc54f83a03373 · schema v1 · pii pii-v1
Full breach record for Arban & Carosi →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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
Arban Carosi: 1TB customer and company data leaked due to negligence. * * Full employee base: Including names, positions, personal and work email addresses, phone numbers. * * Financial Documentation: Contracts, Invoices, Revenue Data * * Customer base: Customer contact details, project details * * Internal correspondence: Service emails and documents disclosing internal processes and company plans. !! In the screenshots, you can see that we have accessed detailed plans of various buildings, including U.S. Army buildings!! We will publish all the data in a week and everyone can use it for their own purposes.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 30, 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.