HackingTechnologyHealthcareInformationStolen CredentialsCapture Stored DataData ExfiltratedTargetedIdentity (basic)Government IDMediumContained

iSpace

bd_c72f82f63fd808fb · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 5, 2023

Filed

May 31, 2023

To disclose

16 weeks

Affected

2state residents only

Linked

7 filings

Confidence

65%

Full breach record for iSpace →2 incidents on file

iSpace, Inc. notified Montana residents of a data breach occurring between Jan 30 and Feb 5, 2023. Unauthorized access to documents containing names and government IDs occurred. iSpace engaged forensic specialists, notified law enforcement, and offered credit monitoring. Discovery was Feb 5, 2023.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d16 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 6 days

discovery → filing · 16 weeks / 115 days

Jan 30, 2023

Begins

Feb 5, 2023

Discovered

May 31, 2023

Filed

vs. sector median

2 wks faster

This filing is one of 7 about the same incident.View merged incident

A leak claim by lockbit_3 about this victim predates this filing by 96 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitelockbit_3bd_9090e54747705ef42023-02-24 · +96dVerified by operator

Regulatory filings (5) · sorted by filing gap

Indiana State AGbd_44748d19a9a0a5652023-05-31Candidate
HHS OCRbd_6e88473a5249090a2023-05-31Verified
Massachusetts State AGbd_6f652403249375542023-05-31Verified
California State AGbd_84bce63b58a6123e2023-05-31Verified

Show 1 more filing ↓up to 5d gap

New Hampshire State AGbd_988375ac2dd01b8f2023-06-05 · +5dVerified

Name: iSpace
norm: ispace
Domain: ispace.com

Name: iSpace
norm: ispace
Domain: ispace.com
Industry: TechnologyllmHealthcarellm

Discovered: Feb 5, 2023
Breach occurred: Jan 30, 2023 – Feb 5, 2023
Undetected for: 6 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 31, 2023
Affected individuals: 2state-resident count only
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: External
Regulator citations: Notified federal law enforcement
Initial access: valid_credentials

During the incident: Engaged third-party forensic specialists to assist with investigating the nature and scope of the incident
Notified federal law enforcement
Provided access to credit monitoring and identity protection services through IDX
Changes made: Engaged the services of security specialists to assist in examining existing policies and practices relative to data privacy
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 16 weeks(115 days from discovery to filing)
Compliance flags: Leak >90d
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 5 states

View merged incident ↗

Indiana State AGMay 31 · first

HHS OCRMay 31 · first

Massachusetts State AGMay 31 · first

California State AGMay 31 · first

Montana State AGMay 31 · first · this page

New Hampshire State AG+5d

Pattern: first filing May 31 (IN), last Jun 5 (NH) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/OCP/Consumer-notification-letter-324.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 31, 2023
Raw hash: ad306f08ca8f28593a432774b2b465e8421d19d3448c4250d55c96df16610768

Linked disclosures

Ransomware claims (1)

Regulatory filings (5) · sorted by filing gap

Reporting entityiSpace

Victim entityiSpace

Incidentdiscovered Feb 5, 2023

Stated responseEngaged third-party forensic specialists to assist with investigating the nature and scope of the incident

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenancedojmt.gov