Confirmed breach. Intrusion Apr 15, 2025, discovered Apr 15, 2025 — the first regulatory filing landed 314 days later (flagged late). 2,963 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 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2,963
Data types
—
Jurisdictions
2
IN VT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Apr 15, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Apr 15, 2025
Reported by VERMONT AG filing
314 days
🍁Vermont State AGFirst filinglinked via multistate filing link · 100%
Lobar, Inc. reported unauthorized network activity discovered on April 15, 2025. The incident potentially exposed personal information including names and government identifiers. Lobar engaged forensic experts, notified law enforcement, and provided credit monitoring services to affected individuals.
Lobar Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-15 and was reported on 2026-02-24. 1 Indiana residents were affected. 2,963 individuals affected in total.
Affected (this filing): 2,963
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.