MalwareRansomwareData EncryptedCustomer Data InvolvedIDENTITY_BASICIDENTITY_GOVERNMENTFINANCIAL_ACCOUNTMediumContained
William S. Hein & Co., Inc.
bd_7376c74fbd07fb0d · schema v1 · pii pii-v1
Full breach record for William S. Hein & Co., Inc. →William S. Hein & Co., Inc. experienced a ransomware incident on or about April 10, 2024, resulting in limited unauthorized access to IT systems. Two Maryland residents were affected, with impacted data including names, SSNs, driver's license numbers, passport numbers, and financial account information. The company engaged incident response professionals and law enforcement, contained the breach, and is offering 12 months of credit monitoring via CyberScout.
Leak gap clock✗ Leak >180d19 months 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.
Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed2 affectedView incident
A leak claim by inc_ransom about this victim predates this filing by 574 days.View originating leak claim
Source provenance
- Source URL
- https://oag.maryland.gov/resources-info/SBN%20Documents/2025/ITU-376185.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
- Filed at
- Nov 13, 2025
- Raw hash
- 98dce2dd1af09b82a43f1c675d03a9516347700fc82781af3056a6e5746ab02e
Reporting entity
- Name
- The Beckage Firmnorm: the beckage firm
- Domain
- thebeckagefirm.com
Victim entity
- Name
- William S. Hein & Co., Inc.norm: william s hein
- Domain
- wshein.com
Incident
- Discovered
- Apr 10, 2024
- Materiality determined
- —
- Notification sent
- —
- Affected individuals
- 2
- Data types
- IDENTITY_BASICIDENTITY_GOVERNMENTFINANCIAL_ACCOUNT
- Attack vector
- Ransomware
- MITRE ATT&CK
- T1486 Data Encrypted for Impact
- Threat actor
- ExternalFinancial
Compliance
- Time to disclose
- 19 months(582 days from discovery to filing)
- Compliance flags
- Leak >180d
- 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.