Confirmed breach. Intrusion May 4, 2024–May 5, 2024, discovered May 4, 2024 — the first regulatory filing landed 26 days later. 4,500 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 >14 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Affected (total reported)
4,500
Data types
5
Identity (basic) · Government ID · Financial account
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
May 4, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discovered
May 4, 2024
Reported by VERMONT AG filing
🏎️Indiana State AGFirst filinglinked via multistate filing link · 95%
Oldenburg Group Incorporated reported a data breach to the Indiana Attorney General. The breach occurred on 2024-05-04 and was reported on 2024-05-30. 5 Indiana residents were affected. 4,500 individuals affected in total.
Oldenburg Group Incorporated reported a ransomware incident between May 4-5, 2024, attributed to the Play ransomware group. Attackers installed ransomware on primary servers and may have accessed personal information. Data potentially exposed includes names, SSNs, driver's license numbers, financial account info, tax info, and medical/health insurance information. The company engaged forensic investigators and IT services, enhanced security protocols, and offered 12 months of credit monitoring.
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.