HRB Tax Group Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-13 and was reported on 2024-11-26. 899 Indiana residents were affected. 25,566 individuals affected in total.
Affected (this filing): 25,566
Clustered 2 filings across 2 jurisdictions · filing window Nov 26, 2024 → Nov 27, 2024. View entity profile → Other incidents for this victim →
incident inc_f56e78787e124d75 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
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.
Identity (basic) · Government ID · Financial account
IN VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 13, 2024
When the intrusion reportedly occurred, per the linked filings
Aug 9, 2024
Reported by VERMONT AG filing
HRB Tax Group Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-13 and was reported on 2024-11-26. 899 Indiana residents were affected. 25,566 individuals affected in total.
Affected (this filing): 25,566
H&R Block notified Vermont consumers of a data breach where an unauthorized third party used stolen PII to access client accounts between May 13 and August 7, 2024. The incident involved names, SSNs, and financial data. H&R Block terminated access, engaged forensic experts, and offered 24 months of identity protection services.
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.