Clustered 2 filings across 2 jurisdictions · filed May 11, 2026. View entity profile → Other incidents for this victim →
incident inc_e2d64966ad7b4e24 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME TX
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 20, 2026
Reported by MAINE AG, TEXAS AG filings
Lamb-Star Engineering, LLC reported an external system breach (hacking) occurring on January 20, 2026, discovered the same day. The incident affected 459 individuals, including 4 Maine residents. The company provided written notification on May 11, 2026, and offered 12 months of credit monitoring and identity theft protection services through Kroll.
Affected (this filing): 459
Lamb-Star Engineering, LLC based in Frisco, Texas, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-01-20 and reported on 2026-05-11. 415 Texas residents were affected. 459 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Health Insurance Information;Other;Date of Birth. Consumers were notified via U.S. Mail.
Affected (this filing): 415
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.