DisclosureLens
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Incident · single filing

State of Rhode Island — February 2026 breach

One linked filing — more sources may join as they report · filed Mar 20, 2026. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

18,000

First → last filing

Mar 20, 2026

incident inc_a4afdf513ae343a8 · merged by deterministic

Confirmed breach. Intrusion Feb 25, 2026, discovered Feb 28, 2026 — the first regulatory filing landed 20 days later. 18,000 individuals reported across the linked filings.

Litigation Timing

Notification delay
20days

Discovered → first regulatory filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing spanno leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksRhode Island RI AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 25, 2026breach begins
Feb 28, 2026discovered
notification delay · 20 days
Mar 20, 2026first & only filing
watching for filings

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

Member cascade — every filing about this breach

  1. MAR 20RI AGRI AG noticeonly filing · 18,000 RI residentsday 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 25, 2026
RI AG
Discovered
Feb 28, 2026· 3d undetected
RI AG
Data types
Government ID · Identity (basic)
RI AG
Attack vector
Misconfiguration
RI AG
Response
Secured Experian to provide a dedicated call center, credit monitoring, and other remediation services · Distributed individual notifications to potentially affected individuals through U.S. mail, postage pre-paid, and in security envelopes
RI AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.