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

Rain Bird Corporation — February 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Dec 11, 2025 → Dec 12, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

24,862

First → last filing

Dec 11, 2025 → Dec 12, 2025

Merge confidence

100%

incident inc_8ce0e39ece764d2f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Feb 5, 2025–Sep 5, 2025, discovered Jul 25, 2025 — the first regulatory filing landed 139 days later (flagged late). 24,862 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
139days

Discovered → first regulatory filing

Discovery variance
112days

Range of discovered_at dates across filings

Filing span
1days

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 clocksMaine✗ ME AG >90d · 139dWashington✗ WA AG >90dVermont✗ VT AG >45 bdayOregon✓ OR AG ≤45dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Feb 5, 2025breach begins
Jul 25, 2025discovered · members disagree
notification delay · 139 days
Dec 11, 2025first filing
Dec 12, 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. DEC 11ME AGME AG noticefirst filing · states nationwide total 24,862day 0
  2. DEC 11IN AGIN AG noticestates nationwide total 24,862day 0
  3. DEC 11WA AGWA AG notice1,293 WA residentsday 0
  4. DEC 11NE AGNE AG notice378 NE residentsday 0
  5. DEC 11VT AGVT AG noticeno count statedday 0
  6. DEC 11OR AGOR AG noticestates nationwide total 24,862day 0
  7. DEC 11NH AGNH AG notice99 NH residentsday 0
  8. DEC 11CA AGCA AG noticeno count statedday 0
  9. DEC 11MT AGMT AG notice330 MT residentsday 0
  10. DEC 11MA AGMA AG notice454 MA residentsday 0
  11. DEC 12TX AGTX AG noticemost recent · states nationwide total 24,862+1d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 11, 2025 – Sep 5, 2025
ME AG
Discovered
Jul 25, 2025ME AG + WA AG + NE AG +3Nov 14, 2025OR AG + TX AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
ME AG + NE AG + VT AG +6
Attack vector
Unauthorized Access
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)

24,862

Sum of filed state slices

6,163· 24.8% of stated

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

US24,862
TX3,255
WA1,293
MA454
NE378
MT330
IN314
NH99
ME40

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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