Matrix Document Imaging
bd_0741528e24426295 · schema v1 · pii pii-v2
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p 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
Company description · AI-generated by the aggregator, not the leak post
N/A I don't have verified, reliable information about a specific company operating under the name "LEGAL-RECORDS.US." This appears to be a domain name rather than a confirmed, well-documented business entity I can factually describe. Domains with names like this are sometimes associated with public records aggregation services, but without verified details on the operating company, registration, or legitimate business activity, I cannot provide an accurate description. Providing fabricated details about its operations, industry classification, or country of incorporation would risk inaccuracy, which is particularly important to avoid in a threat intelligence context where such domains can also be associated with phishing, data scraping, or scam operations. If you have additional context (such as WHOIS data, SSL certificate details, associated IP addresses, or corporate filings), I could help analyze those spec
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 21, 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.