Ursus, Inc. — March 2016 breach

Clustered 4 filings across 4 jurisdictions · filing window Sep 8, 2016 → Sep 19, 2016. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

222

First → last filing

Sep 8, 2016 → Sep 19, 2016

Merge confidence

100%

incident inc_cea5ad19862a4b5c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a phishing attack. Intrusion Mar 21, 2016–Apr 25, 2016, discovered Apr 25, 2016 — the first regulatory filing landed 136 days later (flagged late). 222 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 11-day schedule across 4 filings beginning Sep 8, 2016. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

136days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

11days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 143dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.