DisclosureLens
Leak SiteState AGConfirmed7 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedragnarlockerhigh sensitivity
Merged incident · 7 records

PRIMARY RESIDENTIAL MORTGAGE, INC. — August 2021 breach

Clustered 7 records across 5 jurisdictions: 5 filings and 2 leak-site claims · filed Oct 27, 2021. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

7 records

States

5

Affected · reported

59,559

First → last filing

Oct 27, 2021

Merge confidence

100%

incident inc_78f4277a40e34150 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Aug 8, 2021, discovered Aug 8, 2021 — the first regulatory filing landed 80 days later. 59,559 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
80days

Discovered → first regulatory filing

Discovery variance
50days

Range of discovered_at dates across filings

Leak precedence
46days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
0days

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 >30dWashington⏱ WA AG >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 8, 2021breach begins
Aug 8, 2021discovered · members disagree
notification delay · 80 days
Oct 27, 2021first filing
—watching for filings

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

Member cascade — every filing and leak-site claim in this incident

  1. SEP 11Leak siteragnarlocker postfirst record · attacker claim · unverifiedday 0
  2. SEP 14Leak siteragnarlocker postattacker claim · unverified+3d
  3. OCT 27CA AGCA AG noticeno count stated+46d
  4. OCT 27MT AGMT AG notice48 MT residents+46d
  5. OCT 27WA AGWA AG notice1,712 WA residents+46d
  6. OCT 27MA AGMA AG notice701 MA residents+46d
  7. OCT 27ME AGME AG noticemost recent · states nationwide total 59,559+46d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 8, 2021
CA AG
Discovered
Aug 8, 2021CA AG + MT AG + WA AGSep 27, 2021ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
CA AG + MT AG + WA AG +2
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)

59,559

Sum of filed state slices

2,914· 4.9% of stated

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

US59,559
WA1,712
MA701
ME453
MT48

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 filing5 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 Jun 12, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.