MW Components
bd_2f2ea2a07ebd3549 · schema v1 · pii pii-v1
Full breach record for MW Components →2 incidents on fileMW Components disclosed a ransomware attack where an unauthorized third party accessed systems between March 1 and March 26, 2023. The company discovered the incident on March 26, 2023. Personal information, including basic identity data, may have been acquired. The company engaged forensic investigators, notified law enforcement, and offered one year of credit monitoring to affected individuals.
J jump to incidentP pin to compareR raw source
Incident timeline
Mar 1, 2023
Begins
Mar 26, 2023
Discovered
Jul 28, 2023
Filed
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteblacksuitbd_7c646ecd17cfb9c42023-04-18 · +101dVerified by operator
Regulatory filings (8) · sorted by filing gap
- Indiana State AGbd_2ba967fa047ad15e2023-07-28Candidate
- Massachusetts State AGbd_942fc7aeb5dacbb42023-07-28Verified
- New Hampshire State AGbd_dce2bfbf462b07782023-08-01 · +4dVerified
- Vermont State AGbd_961842e4dc0b2aad2023-08-28 · +31dVerified
Show 4 more filings ↓Show fewer ↑up to 208d gap
- Maine State AGbd_5cf56f6afff3cbc62023-08-29 · +32dVerified
- California State AGbd_e09ff3bc5f2bd8f22023-08-29 · +32dVerified
- New Hampshire State AGbd_5ee69a804aecb5472023-08-30 · +33dVerified
- Illinois State AGbd_4a805e56cbe3021a2023-01-01 · +208dVerified by operator
Filing propagation · 9 filings · 7 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Aug 30 (NH) — a 241-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.