DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

REIC Rentals — February 2026 breach

Clustered 10 filings across 9 jurisdictions · filing window Apr 7, 2026 → May 18, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

3,671

First → last filing

Apr 7, 2026 → May 18, 2026

Merge confidence

100%

incident inc_6f3e517f93634208 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Feb 3, 2026–Feb 5, 2026, discovered Feb 3, 2026 — the first regulatory filing landed 63 days later (flagged late). 3,671 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 2 more. Notifications rolled out on a 41-day schedule across 10 filings beginning Apr 7, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
63days

Discovered → first regulatory filing

Discovery variance
20days

Range of discovered_at dates across filings

Filing span
41days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksOregon✗ OR AG >45dWashington✗ WA AG >90dMaine⏱ ME AG >30d · 63dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 3, 2026breach begins
Feb 3, 2026discovered · members disagree
notification delay · 63 days
Apr 7, 2026first filing
May 18, 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. APR 7VT AGVT AG noticefirst filing · 1 VT residentsday 0
  2. APR 7ME AGME AG notice1 ME residentsday 0
  3. APR 7IN AGIN AG noticestates nationwide total 2,172day 0
  4. APR 7NH AGNH AG notice2 NH residentsday 0
  5. APR 7MT AGMT AG notice519 MT residentsday 0
  6. APR 7IN AGIN AG noticestates nationwide total 2,172day 0
  7. APR 7MA AGMA AG noticeno count statedday 0
  8. APR 7NE AGNE AG notice1 NE residentsday 0
  9. MAY 18OR AGOR AG noticestates nationwide total 3,671+41d
  10. MAY 18WA AGWA AG noticemost recent · 586 WA residents+41d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 3, 2026 – Feb 5, 2026
VT AG
Discovered
Feb 3, 2026ME AG + NE AGFeb 6, 2026WA AGFeb 23, 2026MT AG + OR AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PHI · PII
VT AG + ME AG + NH AG +4
Attack vector
Unauthorized Access
VT 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)

3,671

Sum of filed state slices

1,111· 30.3% of stated

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

US3,671
WA586
MT519
NH2
VT1
ME1
IN1
NE1

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

41 days

Cadence

~1 / 4.6d

vs. multi-state median

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