DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedworldleakshigh sensitivity
Merged incident · 7 records

SAPP BROS., INC. — August 2025 breach

Clustered 7 records across 5 jurisdictions: 6 filings and 1 leak-site claim · filing window Dec 10, 2025 → Dec 11, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 records

States

5

Affected · reported

16,292

First → last dated filing

Dec 10, 2025 → Dec 11, 2025

Merge confidence

100%

incident inc_8d5dca65fe0d4a85 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 25, 2025, discovered Aug 25, 2025. 16,292 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
77days

Range of discovered_at dates across filings

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 25, 2025breach begins
Aug 25, 2025discovered · members disagree
Dec 10, 2025first dated filing
Dec 11, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. AUG 29Leak siteworldleaks postfirst record · attacker claim · unverifiedday 0
  2. DEC 1IL AGIL AG noticefiling day not on record · no count stated—
  3. DEC 10NE AGNE AG noticefiling day not on record · no count stated—
  4. DEC 10IN AGIN AG noticestates nationwide total 16,292+103d
  5. DEC 11IA AGIA AG noticestates nationwide total 16,292+104d
  6. DEC 11MT AGMT AG noticemost recent · 7 MT residents+104d
  7. MAR 24NE AGNE AG noticefiling day not on record · no count stated—
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 25, 2025
IN AG
Discovered
Aug 25, 2025NE AG + IA AG + MT AGNov 10, 2025IL AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
IL AG + IA AG + NE AG +1
Attack vector
Unauthorized Access
NE AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

16,292

Sum of filed state slices

1,756· 10.8% of stated

89% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US16,292
IA1,741
IN8
MT7

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 29, 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

1 days

Cadence

~1 / 0.5d

vs. multi-state median

6.0× faster

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.