All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

VT Group

Clustered 2 filings across 2 jurisdictions · filing window Mar 3, 2017 → Mar 8, 2017. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Mar 3, 2017 → Mar 8, 2017

Merge confidence

100%

incident inc_a80da58748cb4243 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Discovered Oct 4, 2016 — the first regulatory filing landed 150 days later. 20 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

150days

Discovered → first regulatory filing

Filing span

5days

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.

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown

Oct 4, 2016discovered

notification delay · 150 days

Mar 3, 2017first filing

Mar 8, 2017most recent filing

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

Member cascade — every filing about this breach

MAR 3NH AGNH AG noticefirst filing · 8 NH residentsday 0
MAR 8MA AGMA AG noticemost recent · 12 MA residentsauto-linked+5d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: —
Discovered: Oct 4, 2016
Data types: Identity (basic) · Government ID · Financial account
Attack vector: Unauthorized Access

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

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 filing2 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

5 days

vs. multi-state median

1.6× faster

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.