DisclosureLens
State AGConfirmed3 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 3 filings

Perry Johnson Mortgage Company, Inc. — March 2023 breach

Clustered 3 filings across 3 jurisdictions · filing window Jul 15, 2024 Jul 26, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

1,207

First → last filing

Jul 15, 2024 Jul 26, 2024

Merge confidence

100%

incident inc_2e6f6d4b7c874c2a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filings describe a third-party compromise. Intrusion Mar 27, 2023–May 2, 2023, discovered May 1, 2024 — the first regulatory filing landed 75 days later. 1,207 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, and PII. Notifications rolled out on a 11-day schedule across 3 filings beginning Jul 15, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
75days

Discovered → first regulatory filing

Discovery variance
44days

Range of discovered_at dates across filings

Filing span
11days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >30d · 31dFull clock table in Litigation Timeline

Incident timeline

Mar 27, 2023breach begins
May 1, 2024discovered · members disagree
notification delay · 75 days
Jul 15, 2024first filing
Jul 26, 2024most 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. JUL 15ME AGME AG noticefirst filing · states nationwide total 1,207day 0
  2. JUL 22MT AGMT AG notice9 MT residents+7d
  3. JUL 26IN AGIN AG noticemost recent · states nationwide total 1,184+11d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 27, 2023May 2, 2023
ME AG
Discovered
May 1, 2024MT AGJun 14, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · PII
ME AG + MT AG
Attack vector
Third-Party / Supply Chain
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)

1,207

Sum of filed state slices

22· 1.8% of stated

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

US1,207
ME11
MT9
IN2

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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
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

11 days

Cadence

~1 / 5.5d

vs. multi-state median

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