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

South Carolina Department of Revenue — September 2012 breach

Clustered 3 filings across 3 jurisdictions · filing window Nov 26, 2012 → Dec 10, 2012. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

3,581

First → last filing

Nov 26, 2012 → Dec 10, 2012

Merge confidence

100%

incident inc_e13ad270d60c4316 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe hacking. Intrusion Sep 1, 2012–Sep 30, 2012, discovered Oct 1, 2012 — the first regulatory filing landed 56 days later. 3,581 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 1 more. Notifications rolled out on a 14-day schedule across 3 filings beginning Nov 26, 2012. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
56days

Discovered → first regulatory filing

Discovery variance
9days

Range of discovered_at dates across filings

Filing span
14days

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 clocksHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Sep 1, 2012breach begins
Oct 1, 2012discovered · members disagree
notification delay · 56 days
Nov 26, 2012first filing
Dec 10, 2012most 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. NOV 26NH AGNH AG noticefirst filing · 1,445 NH residentsday 0
  2. NOV 28HI AGHI AG notice2,136 HI residents+2d
  3. DEC 10CA AGCA AG noticemost recent · no count stated+14d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 1, 2012 – Sep 30, 2012
NH AG
Discovered
Oct 1, 2012NH AG + HI AGOct 10, 2012CA AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Government ID · PII
NH AG + HI AG + CA 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
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

14 days

Cadence

~1 / 7d

vs. multi-state median

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