DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressHHS OCRState AGConfirmed12 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 12 filings

Fieldtex Products Inc. — August 2025 breach

Clustered 12 filings across 6 jurisdictions · filing window Aug 19, 2025 → Dec 24, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

5

Affected · reported

238,615

First → last filing

Aug 19, 2025 → Dec 24, 2025

Merge confidence

100%

incident inc_c15fc0d5fe1a428d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings, 1 press report and 2 unverified claims. The filings describe unauthorized access. Intrusion Aug 19, 2025, discovered Aug 19, 2025 — the first regulatory filing landed 93 days later. 238,615 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 127-day schedule across 9 filings beginning Aug 19, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
93days

Discovered → first regulatory filing

Discovery variance
104days

Range of discovered_at dates across filings

Leak precedence
93days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
127days

Time between earliest and latest filing

Not recorded for this incident

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

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

Sensitive data

identity_government

Incident timeline

Aug 19, 2025breach begins
Aug 19, 2025discovered · members disagree
notification delay · 93 days
Nov 20, 2025first filing
Dec 24, 2025most 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 19Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. NOV 5Leak siteakira postattacker claim · unverified+78d
  3. NOV 20HHS OCRHHS OCR noticestates nationwide total 238,615+93d
  4. DEC 1IL AGIL AG noticeno count stated+104d
  5. DEC 3HHS OCRHHS OCR noticestates nationwide total 20,641+106d
  6. DEC 3HHS OCRHHS OCR noticestates nationwide total 5,901+106d
  7. DEC 3HHS OCRHHS OCR noticestates nationwide total 9,206+106d
  8. DEC 4SC AGSC AG notice9,132 SC residents+107d
  9. DEC 12HHS OCRHHS OCR noticestates nationwide total 104,071+115d
  10. DEC 17TX AGTX AG noticestates nationwide total 95,362+120d
  11. DEC 24MA AGMA AG noticemost recent · 2 MA residents+127d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 19, 2025
TX AG
Discovered
Aug 19, 2025SC AGDec 1, 2025IL AG + TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + SC AG + TX AG +2
Attack vector
Unauthorized Access
HHS OCR

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)

238,615

Sum of filed state slices

9,459· 4.0% of stated

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

US238,615
SC9,132
TX325
MA2

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 claim2 members

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

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing9 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 Aug 22, 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

127 days

Cadence

~1 / 11.5d

vs. multi-state median

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