DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed13 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedthegentlemenhigh sensitivity
Merged incident · 13 records

JRK Property Holdings Inc — March 2026 breach

Clustered 13 records across 10 jurisdictions: 12 filings and 1 leak-site claim · filing window May 11, 2026 → Aug 4, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 records

States

10

Affected · reported

113,641

First → last dated filing

May 11, 2026 → Aug 4, 2026

Merge confidence

100%

incident inc_40812245659f4d05 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Mar 26, 2026–Apr 22, 2026, discovered Mar 26, 2026. 113,641 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 85-day schedule across 10 dated filings beginning May 11, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
85days

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 clocksWashington✗ WA AG >90dTexas✗ TX AG >30dOregon✗ OR AG >45dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 26, 2026breach begins
Mar 26, 2026discovered
May 11, 2026first dated filing
Aug 4, 2026most 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. APR 4Leak sitethegentlemen postfirst record · attacker claim · unverifiedday 0
  2. MAY 5NE AGNE AG noticefiling day not on record · 1 NE residents—
  3. MAY 11NH AGNH AG notice1 NH residents+36d
  4. MAY 12MA AGMA AG notice4,328 MA residents+37d
  5. JUL 24IN AGIN AG noticestates nationwide total 113,641+110d
  6. JUL 24NE AGNE AG noticefiling day not on record · 1,032 NE residents—
  7. JUL 27SC AGSC AG notice1,154 SC residents+113d
  8. JUL 27WA AGWA AG notice5,667 WA residents+113d
  9. JUL 27CA AGCA AG noticeno count stated+113d
  10. JUL 27NH AGNH AG notice396 NH residents+113d
  11. JUL 28TX AGTX AG noticestates nationwide total 113,641+114d
  12. JUL 28VT AGVT AG notice48 VT residents+114d
  13. AUG 4OR AGOR AG noticemost recent · states nationwide total 1,494+121d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 26, 2026
IN AG
Discovered
Mar 26, 2026
NE AG + NH AG + SC AG +4
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI
NE AG + NH AG + MA AG +5
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)

113,641

Sum of filed state slices

24,259· 21.3% of stated

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

US113,641
TX11,120
WA5,667
MA4,328
SC1,154
NE1,032
IN514
NH396
VT48

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 filing12 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 23, 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

85 days

Cadence

~1 / 9.4d

vs. multi-state median

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