Clustered 3 filings across 3 jurisdictions · filing window Mar 26, 2026 → Jun 22, 2026. View entity profile → Other incidents for this victim →
incident inc_1cfab195ce6043e3 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN TX
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 27, 2026
When the intrusion reportedly occurred, per the linked filings
Ludlum Measurements, Inc. (LMI), founded in 1962 in Sweetwater, Texas, designs, manufactures, and supplies radiation detection and measurement equipment used w... - We have 5 TB data including full source codes, client data, and more.
Apr 29, 2026
Reported by TEXAS AG filing
Ludlum Measurements Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-27 and was reported on 2026-06-19. 3 Indiana residents were affected. 3,191 individuals affected in total.
Ludlum Measurements, Inc. based in Sweetwater, Texas, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2026-04-29 and reported on 2026-06-22. 2,708 Texas residents were affected. 3,191 individuals affected in total. Types of information involved: Name of individual;Social Security Number Information;Government-issued ID number (e.g. passport, state ID card);Financial Information (e.g. account number, credit or debit card number);Health Insurance Information. Consumers were notified via U.S. Mail.
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,191
Affected (this filing): 2,708