Takeda Pharmaceuticals U.S.A. Inc - The Lash Group reported a data breach to the Montana Attorney General. The breach was reported on 2024-05-31. The breach occurred on 4/10/2024. 91 Montana residents were affected.
Affected (this filing): 91
Clustered 2 filings across 2 jurisdictions · filed May 31, 2024. View entity profile → Other incidents for this victim →
incident inc_d7185b63538b4b20 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
MT WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 10, 2024
When the intrusion reportedly occurred, per the linked filings
Apr 10, 2024
Reported by WASHINGTON AG filing
Takeda Pharmaceuticals U.S.A. Inc - The Lash Group reported a data breach to the Montana Attorney General. The breach was reported on 2024-05-31. The breach occurred on 4/10/2024. 91 Montana residents were affected.
Affected (this filing): 91
Takeda Pharmaceuticals U.S.A., Inc. (The Lash Group, LLC), a health sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2024-04-10 and filed notice on 2024-05-31. 889 Washington residents were affected. 51 days elapsed between awareness and notification. 49 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 889
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.