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

CNG Financial Corporation Inc — July 2018 breach

Clustered 5 filings across 5 jurisdictions · filing window Aug 3, 2018 → Aug 28, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

14,364

First → last filing

Aug 3, 2018 → Aug 28, 2018

Merge confidence

100%

incident inc_6d35677c305e45d2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a third-party compromise. Intrusion Jul 11, 2018–Jul 16, 2018, discovered Jul 16, 2018 — the first regulatory filing landed 18 days later. 14,364 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial, and 1 more. Notifications rolled out on a 25-day schedule across 5 filings beginning Aug 3, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
18days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
25days

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 clocksCalifornia✓ CA 60-day OK · 30dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 11, 2018breach begins
Jul 16, 2018discovered
notification delay · 18 days
Aug 3, 2018first filing
Aug 28, 2018most 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. AUG 3NH AGNH AG noticefirst filing · 1 NH residentsday 0
  2. AUG 15MT AGMT AG notice4 MT residents+12d
  3. AUG 15CA AGCA AG noticeno count stated+12d
  4. AUG 15MA AGMA AG notice4 MA residents+12d
  5. AUG 28SC AGSC AG noticemost recent · 14,359 SC residents+25d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 11, 2018 – Jul 16, 2018
NH AG
Discovered
Jul 16, 2018· 5d undetected
NH AG + MT AG + CA AG +1
Data types
Financial · Financial account · Identity (basic) · Government ID
NH AG + MT AG + CA AG +2
Attack vector
Third-Party / Supply Chain
NH AG

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

Affected residents by state

per-state reported counts

SC14,359
MT4
MA4
NH1

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing5 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
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

25 days

Cadence

~1 / 6.3d

vs. multi-state median

2.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.