iSpace
bd_9090e54747705ef4 · schema v1 · pii pii-v1
Full breach record for iSpace →2 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group LockBit 3.x 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.
Sanctions caution: LockBit 3.x carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.
Source: Ransomware.live
Post text · scraped from the leak site
iSpace is a leading technology and business process services company serving the healthcare, automotive, entertainment and financial services industries. Founded in 2000, our more than 600 professionals worldwide serve more than 25 Fortune 500 compan...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Feb 24, 2023
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Indiana State AGbd_44748d19a9a0a5652023-05-31 · +96dCandidate
- HHS OCRbd_6e88473a5249090a2023-05-31 · +96dVerified
- Massachusetts State AGbd_6f652403249375542023-05-31 · +96dVerified
- California State AGbd_84bce63b58a6123e2023-05-31 · +96dVerified
Show 2 more filings ↓Show fewer ↑up to 101d gap
- Montana State AGbd_c72f82f63fd808fb2023-05-31 · +96dVerified
- New Hampshire State AGbd_988375ac2dd01b8f2023-06-05 · +101dVerified
Filing propagation · 7 filings · 5 states
View merged incident ↗Pattern: first filing Feb 24, last Jun 5 (NH) — a 101-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.
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.