FEDERALMalwareRansomwareData EncryptedRansom DemandedLowContained
SCANSOURCE, INC.
bd_94e32d5ef83030c4 · schema v1 · pii pii-v1
Full breach record for SCANSOURCE, INC. →ScanSource, Inc. disclosed a cyberattack discovered on May 14, 2023, that impacted its core hardware systems. The incident involved ransomware, leading to system disruption until restoration on May 26, 2023. The company launched its incident response plan and engaged external experts. No specific data types or individual counts were disclosed in this financial results filing.
Leak gap clock⏱ Leak >30d14 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 2 about the same incident.View merged incident
A leak claim by cactus about this victim predates this filing by 33 days.View originating leak claim
Linked disclosures
Why this link?Ransomware claims (1)
- bd_6a943a8292a9b35dLeak Sitecactusfiled 2023-07-20(33d gap)Verified by operator
Source provenance
- Source URL
- https://www.sec.gov/Archives/edgar/data/918965/000091896523000021/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
- Filed at
- Aug 22, 2023
- Raw hash
- 4bb10982aa04ce4c8dc96028cb3d1f656500a2dc31349ad9e3388a55089a90b6
Source filing
AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.
Reporting entity
- Name
- SCANSOURCE, INC.norm: scansource
Victim entity
- Name
- SCANSOURCE, INC.norm: scansource
Incident
- Discovered
- May 14, 2023
- Materiality determined
- Aug 22, 2023
- Notification sent
- Aug 22, 2023
- Affected individuals
- Not disclosed
- Data types
- —
- Attack vector
- Unauthorized Access
- MITRE ATT&CK
- T1486 Data Encrypted for ImpactT1078 Valid Accounts
- Threat actor
- ExternalFinancial
- Initial access
- valid_credentials
Compliance
- Time to disclose
- 14 weeks(100 days from discovery to filing)
- Compliance flags
- Leak >30dSEC 4-day OK · 0d
- 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.
- Clock breakdown
Statute Window Elapsed Threshold Status SEC Materiality determined: Aug 22, 2023→ Filed: Aug 22, 20230d cal. 4 business days SEC 4-day OK
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.