DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlynxhigh sensitivity
Merged incident · 11 filings

PACIFIC RESIDENTIAL MORTGAGE, LLC — February 2025 breach

Clustered 11 filings across 10 jurisdictions · filing window Feb 9, 2025 → Apr 23, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

35,525

First → last filing

Feb 9, 2025 → Apr 23, 2026

Merge confidence

100%

incident inc_995e86da583b4851 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. The filings describe malware. Intrusion Feb 10, 2025–Feb 20, 2025, discovered Feb 10, 2025 — the first regulatory filing landed 43 days later (flagged late). 35,525 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 438-day schedule across 9 filings beginning Feb 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
43days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
44days 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
438days

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 >30d · 44dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 10, 2025breach begins
Feb 10, 2025discovered
notification delay · 43 days
Mar 25, 2025first filing
Apr 23, 2026most 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. FEB 9Leak sitelynx postfirst filing · attacker claim · unverifiedday 0
  2. FEB 9Leak sitelynx postattacker claim · unverifiedday 0
  3. MAR 25NE AGNE AG noticeno count stated+44d
  4. MAR 25IN AGIN AG noticestates nationwide total 35,525+44d
  5. MAR 26MA AGMA AG notice12 MA residents+45d
  6. MAR 26ME AGME AG noticestates nationwide total 35,525+45d
  7. MAR 26WA AGWA AG notice2,088 WA residents+45d
  8. MAR 26CA AGCA AG noticeno count stated+45d
  9. MAR 26OR AGOR AG noticestates nationwide total 35,525+45d
  10. APR 3NH AGNH AG notice2 NH residents+53d
  11. APR 23MD AGMD AG noticemost recent · 7 MD residents+438d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 10, 2025
IN AG
Discovered
Feb 10, 2025
NE AG + ME AG + WA AG +4
Data types
Identity (basic) · Government ID · Financial account
NE AG + ME AG + WA AG +4
Attack vector
Ransomware
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)

35,525

Sum of filed state slices

2,272· 6.4% of stated

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

US35,525
WA2,088
IN160
MA12
MD7
ME3
NH2

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 report

No press coverage linked yet.

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

438 days

Cadence

~1 / 43.8d

vs. multi-state median

54.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.