DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

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

4

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

Sensitive data

identity_government

Incident timeline

Mar 21, 2016breach begins
Apr 25, 2016discovered
notification delay · 136 days
Sep 8, 2016first filing
Sep 19, 2016most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. SEP 8NH AGNH AG noticefirst filing · 42 NH residentsday 0
  2. SEP 12MA AGMA AG notice174 MA residents+4d
  3. SEP 15MT AGMT AG notice6 MT residents+7d
  4. SEP 19CA AGCA AG noticemost recent · no count stated+11d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 21, 2016
NH AG
Discovered
Apr 25, 2016· 35d undetected
NH AG + MT AG + CA AG
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
NH AG + MT AG + CA AG +1
Attack vector
Phishing
NH AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

MA174
NH42
MT6

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

11 days

Cadence

~1 / 3.7d

vs. multi-state median

1.4× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.