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

Sterling BackCheck — May 2015 breach

Clustered 6 filings across 5 jurisdictions · filing window Jul 31, 2015 → Aug 11, 2015. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

5,728

First → last filing

Jul 31, 2015 → Aug 11, 2015

Merge confidence

100%

incident inc_6671f512083d4199 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filing describes unauthorized access. Intrusion May 29, 2015, discovered May 29, 2015 — the first regulatory filing landed 63 days later. 5,728 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 11-day schedule across 6 filings beginning Jul 31, 2015. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
63days

Discovered → first regulatory filing

Discovery variance
1days

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 clocksSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 29, 2015breach begins
May 29, 2015discovered · members disagree
notification delay · 63 days
Jul 31, 2015first filing
Aug 11, 2015most 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 31NH AGNH AG noticefirst filing · no count statedday 0
  2. AUG 3SC AGSC AG notice1,661 SC residents+3d
  3. AUG 4MA AGMA AG notice1,914 MA residents+4d
  4. AUG 7NH AGNH AG notice734 NH residents+7d
  5. AUG 7CA AGCA AG noticeno count stated+7d
  6. AUG 11WA AGWA AG noticemost recent · 1,419 WA residents+11d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2015
NH AG
Discovered
May 29, 2015SC AGMay 30, 2015NH AG + WA AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
NH AG + SC AG + CA AG +2
Attack vector
Unauthorized Access
SC 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

MA1,914
SC1,661
WA1,419
NH734

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

11 days

Cadence

~1 / 2.2d

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.