Vomela Specialty Company reported a data breach to the Indiana Attorney General. The breach occurred on 2024-12-19 and was reported on 2025-02-10. 1 Indiana residents were affected. 794 individuals affected in total.
Affected (this filing): 794
Clustered 2 filings across 2 jurisdictions · filed Feb 10, 2025. View entity profile → Other incidents for this victim →
incident inc_8171dbaf63b044f2 · 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
IN MD
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 19, 2024
When the intrusion reportedly occurred, per the linked filings
Dec 21, 2024
Reported by MARYLAND AG filing
Vomela Specialty Company reported a data breach to the Indiana Attorney General. The breach occurred on 2024-12-19 and was reported on 2025-02-10. 1 Indiana residents were affected. 794 individuals affected in total.
Affected (this filing): 794
Vomela Specialty Company notified the Maryland AG of a data event affecting 1 Maryland resident. Unauthorized access occurred between Dec 19-21, 2024, resulting in the download of files containing names and Social Security numbers. The company notified federal law enforcement and offered 12 months of credit monitoring via TransUnion.
Affected (this filing): 1
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.