US-Saudi Arabian Business Council
bd_b61f2da1c0a43801 · schema v1 · pii pii-v1
Full breach record for US-Saudi Arabian Business Council →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
Facilitating hundreds of millions of dollars in cross-border trade and investment agreements between the U.S. and Saudi Arabia for 30 years. Informing, counseling, and connecting thousands of U.S. and Saudi companies to increase cross-border trade and investment. In the course of a successful cyber attack on this company, we have a large amount of confidential information at our disposal. All financial documents, mail correspondence, agreements and contracts that are not subject to disclosure, personal data of employees. All this and much more will be published in case we do not come to an agreement.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 17, 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.