All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

ADF International, Inc. — March 2017 breach

Clustered 2 filings across 2 jurisdictions · filing window Mar 13, 2017 → Apr 12, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge95%

Determination

Confirmed

Members

2 filings

States

Affected · reported

308

First → last filing

Mar 13, 2017 → Apr 12, 2017

Merge confidence

95%

incident inc_4e166bfd99244a39 · merged by deterministic · confidence 95%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe social engineering. Intrusion Mar 10, 2017, discovered Mar 13, 2017. 308 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

0days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

30days

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.

Sensitive data

identity_government

Incident timeline

Mar 10, 2017breach begins

Mar 13, 2017discovered

notification delay · 0 days

Mar 13, 2017first filing

Apr 12, 2017most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

MAR 13MT AGMT AG noticefirst filing · 307 MT residentsday 0
APR 12NH AGNH AG noticemost recent · 1 NH residentsauto-linked+30d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 10, 2017
Discovered: Mar 13, 2017· 3d undetected
Data types: Employment · Identity (basic) · Government ID · PII
Attack vector: Third-Party / Supply Chain

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing2 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 0.95 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (95% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

30 days

vs. multi-state median

3.8× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.