GLOBALClaimed by QilinFirst sighting
Posted to leak site Feb 12, 2026bd_75acf5ddcea3ac0d
Clustered 3 filings across 3 jurisdictions · filing window Feb 12, 2026 → Apr 10, 2026. View entity profile → Other incidents for this victim →
incident inc_35301e310c794396 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 22, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 22, 2026
Reported by MAINE AG, NEW HAMPSHIRE AG filings
Segue Manufacturing Services LLC (North Billerica, MA) reported an external system breach (hacking) that occurred and was discovered on January 22, 2026. A total of 400 individuals were affected, including 3 Maine residents. Consumer notifications were sent on March 20, 2026. Affected individuals were offered 24 months of Experian Identity Works identity theft protection.
Segue Manufacturing Services LLC notified the New Hampshire Attorney General on April 10, 2026, of a cybersecurity incident discovered on January 22, 2026. The incident potentially exposed the name, address, and Social Security number of 54 New Hampshire residents. Segue engaged a cyber firm, notified law enforcement, and provided 24 months of complimentary credit monitoring and identity restoration services to affected individuals.
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.
Affected (this filing): 3
Affected (this filing): 54