DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed8 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcicada3301high sensitivity
Merged incident · 8 filings

Riley Pope & Laney LLC — August 2024 breach

Clustered 8 filings across 8 jurisdictions · filing window Aug 14, 2024 → Feb 12, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

7,699

First → last filing

Aug 14, 2024 → Feb 12, 2025

Merge confidence

100%

incident inc_a18d60f422664793 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 11, 2024–Aug 12, 2024, discovered Aug 12, 2024 — the first regulatory filing landed 184 days later (flagged late). 7,699 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 182-day schedule across 7 filings beginning Aug 14, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
184days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
182days 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
182days

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 >180dMaine✗ ME AG >90d · 184dVermont✗ VT AG >45 bdayMaryland✗ MD AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 11, 2024breach begins
Aug 12, 2024discovered
notification delay · 184 days
Feb 12, 2025first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 14Leak sitecicada3301 postfirst filing · attacker claim · unverifiedday 0
  2. FEB 12MA AGMA AG notice10 MA residents+182d
  3. FEB 12MT AGMT AG notice1 MT residents+182d
  4. FEB 12IN AGIN AG noticestates nationwide total 7,699+182d
  5. FEB 12ME AGME AG noticestates nationwide total 7,699+182d
  6. FEB 12VT AGVT AG noticeno count stated+182d
  7. FEB 12MD AGMD AG notice46 MD residents+182d
  8. FEB 12SC AGSC AG noticemost recent · 3,875 SC residents+182d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 11, 2024 – Aug 12, 2024
MT AG
Discovered
Aug 12, 2024· 1d undetected
MT AG + ME AG + VT AG +2
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + MT AG + ME AG +3
Attack vector
Unauthorized Access
MT 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)

7,699

Sum of filed state slices

3,963· 51.5% of stated

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

US7,699
SC3,875
MD46
IN27
MA10
ME4
MT1

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

182 days

Cadence

~1 / 26d

vs. multi-state median

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