HackingData ExfiltratedIDENTITY_BASICPIILowContained
SIRVA, INC.
bd_8b6a98474b8125e9 · schema v1 · pii pii-v1
Full breach record for SIRVA, INC. →Sirva, Inc. notified consumers of a data breach where unknown actors accessed systems and copied files between August 16, 2023, and October 17, 2023. The incident involved personal information of individuals served by Sirva's relocation clients. Sirva engaged in network security assessments, notified law enforcement, and offered 12 months of credit monitoring via Kroll.
Vermont clock✗ VT AG >45 bday43 weeks discovery → filing
⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
This filing is one of 3 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- bd_820efc4a059b0ef4New Hampshire State AGfiled 2024-06-14Verified
- bd_aa0eab70c0f340a7Montana State AGfiled 2024-06-14Candidate
Source provenance
- Source URL
- https://ago.vermont.gov/document/2024-06-14-sirva-inc-data-breach-notice-consumers
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Jun 14, 2024
- Raw hash
- 2e17fad01d7508b4843558cf7c94363a0598b3afb005f4978c292c66f806f39d
Reporting entity
- Name
- SIRVA, INC.norm: sirva
Victim entity
- Name
- SIRVA, INC.norm: sirva
Incident
- Discovered
- Aug 16, 2023
- Materiality determined
- —
- Notification sent
- Jun 14, 2024
- Affected individuals
- Not disclosed
- Data types
- IDENTITY_BASICPII
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1078 Valid AccountsT1119 Automated Collection
- Threat actor
- External
- Regulator citations
- Notified federal law enforcement and regulators
Compliance
- Time to disclose
- 43 weeks(303 days from discovery to filing)
- Compliance flags
- VT AG >45 bday
- Discovery-date grounding
- occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.