Urban One Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-13 and was reported on 2025-12-29. 676 Indiana residents were affected. 1,770 individuals affected in total.
Affected (this filing): 1,770
Clustered 2 filings across 2 jurisdictions · filing window Dec 29, 2025 → Dec 30, 2025. View entity profile → Other incidents for this victim →
incident inc_34c97b2ff7314504 · 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.
IN NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 13, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 15, 2025
Reported by NEW HAMPSHIRE AG filing
Urban One Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-02-13 and was reported on 2025-12-29. 676 Indiana residents were affected. 1,770 individuals affected in total.
Affected (this filing): 1,770
Urban One, Inc. notified the New Hampshire Attorney General of a data security incident affecting 2 NH residents. Unauthorized access occurred starting Feb 13, 2025, via a social engineering campaign leading to data exfiltration. Urban One became aware on March 15, 2025, notified law enforcement, and engaged external experts. Affected data includes employee PII, SSNs, financial accounts, and health info. Notifications mailed Dec 29, 2025, offering 24 months of Experian credit monitoring.
Affected (this filing): 2
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.