Clustered 2 filings across 2 jurisdictions · filing window Mar 7, 2025 → Apr 23, 2026. View entity profile → Other incidents for this victim →
incident inc_ee00d8576e894be4 · 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.
MD NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 2, 2025
When the intrusion reportedly occurred, per the linked filings
Feb 17, 2025
Reported by NEW HAMPSHIRE AG, MARYLAND AG filings
Eckert & Ziegler Isotope Products, Inc. reported a data security incident to the New Hampshire Attorney General. Unauthorized access occurred on Feb 2, 2025, discovered on Feb 17, 2025. Files containing personal information of 3 NH residents were accessed. E&Z engaged forensic investigators, contained the incident, and offered credit monitoring.
Affected (this filing): 3
Eckert & Ziegler Isotope Products, Inc. reported a data security incident to the Maryland Attorney General on March 31, 2025. Unauthorized access occurred on February 2, 2025, and was discovered on February 17, 2025. The incident affected four Maryland residents, exposing names, addresses, dates of birth, Social Security numbers, driver's license numbers, and financial account information. E&Z engaged a forensic firm, contained the incident, and is offering credit monitoring.
Affected (this filing):
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.