Confirmed breach. Intrusion Feb 29, 2024, discovered Feb 29, 2024 — the first regulatory filing landed 85 days later (flagged late). 9,369 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
9,369
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Feb 29, 2024
When the intrusion reportedly occurred, per the linked filings
Sree Hotels, LLC notified consumers on May 24, 2024, of a data security incident discovered on February 29, 2024. An unauthorized third party potentially acquired names and Social Security numbers. Sree engaged forensic specialists, disabled accounts, and offered 24 months of credit monitoring. No evidence of misuse was found at the time of notification.
VT AG >45 bdayLeak >90d
🏎️Indiana State AGMost recentlinked via multistate filing link · 100%
Sree Hotels LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2024-02-29 and was reported on 2024-05-24. 176 Indiana residents were affected. 9,369 individuals affected in total.
Affected (this filing): 9,369
Leak >90d
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.