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

PEÑA BRIONES MCDANIEL & CO. — February 2025 breach

Clustered 8 filings across 5 jurisdictions · filing window Apr 15, 2025 → Sep 18, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

4

Affected · reported

4,594

First → last filing

Apr 15, 2025 → Sep 18, 2025

Merge confidence

100%

incident inc_2c913ee36b664347 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filing describes a phishing attack. Intrusion Feb 12, 2025–Mar 13, 2025, discovered Feb 12, 2025 — the first regulatory filing landed 177 days later (flagged late). 4,594 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 156-day schedule across 7 filings beginning Apr 15, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
177days

Discovered → first regulatory filing

Discovery variance
189days

Range of discovered_at dates across filings

Leak precedence
115days 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
156days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine✗ ME AG >90d · 216dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 12, 2025breach begins
Feb 12, 2025discovered · members disagree
notification delay · 177 days
Aug 8, 2025first filing
Sep 18, 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. APR 15Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. AUG 8IN AGIN AG noticestates nationwide total 4,594+115d
  3. AUG 18MA AGMA AG notice1 MA residents+125d
  4. AUG 19TX AGTX AG noticestates nationwide total 4,594+126d
  5. SEP 16MA AGMA AG notice1 MA residents+154d
  6. SEP 16ME AGME AG noticestates nationwide total 1,757+154d
  7. SEP 16IN AGIN AG noticestates nationwide total 1,757+154d
  8. SEP 18TX AGTX AG noticemost recent · states nationwide total 1,757+156d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 13, 2025
IN AG
Discovered
Feb 12, 2025ME AGJul 11, 2025TX AGAug 20, 2025TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + TX AG + ME AG
Attack vector
Phishing
ME 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)

4,594

Sum of filed state slices

4,184· 91.1% of stated

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

US4,594
TX4,180
IN2
MA1
ME1

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

156 days

Cadence

~1 / 22.3d

vs. multi-state median

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