DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed3 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 3 filings

Comnet Marketing Group — April 2016 breach

Clustered 3 filings across 3 jurisdictions · filing window Jul 11, 2016 → Jul 22, 2016. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

9

First → last filing

Jul 11, 2016 → Jul 22, 2016

Merge confidence

100%

incident inc_39f4a7a013cd41a1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion Apr 22, 2016–Apr 24, 2016, discovered Apr 22, 2016 — the first regulatory filing landed 80 days later (flagged late). 9 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 11-day schedule across 3 filings beginning Jul 11, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
80days

Discovered → first regulatory filing

Discovery variance
62days

Range of discovered_at dates across filings

Filing span
11days

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.

Regulatory clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 22, 2016breach begins
Apr 22, 2016discovered · members disagree
notification delay · 80 days
Jul 11, 2016first filing
Jul 22, 2016most recent filing

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

Member cascade — every filing about this breach

  1. JUL 11NH AGNH AG noticefirst filing · 8 NH residentsday 0
  2. JUL 12MT AGMT AG notice1 MT residents+1d
  3. JUL 22OR AGOR AG noticemost recent · no count stated+11d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 24, 2016
NH AG
Discovered
Apr 22, 2016OR AGApr 24, 2016MT AGJun 23, 2016NH AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
NH AG + MT AG
Attack vector
Unauthorized Access
NH AG

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 filing3 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
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

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

Filing velocity

Spread

11 days

Cadence

~1 / 5.5d

vs. multi-state median

1.4× 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.