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

Confirmed4 filings · 4 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 4 filings

LifeMark Securities Corp. — August 2019 breach

Clustered 4 filings across 4 jurisdictions · filing window Nov 19, 2019 → Nov 25, 2019. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

4 filings

States

Affected · reported

408

First → last filing

Nov 19, 2019 → Nov 25, 2019

Merge confidence

100%

incident inc_e2248b40f08e4bb7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. The filings describe a phishing attack. Intrusion Aug 3, 2019–Aug 27, 2019, discovered Sep 4, 2019 — the first regulatory filing landed 76 days later. 408 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 6-day schedule across 4 filings beginning Nov 19, 2019. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

76days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

6days

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 clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 3, 2019breach begins

Sep 4, 2019discovered

notification delay · 76 days

Nov 19, 2019first filing

Nov 25, 2019most recent filing

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

Member cascade — every filing about this breach

NOV 19MT AGMT AG noticefirst filing · 15 MT residentsday 0
NOV 20NH AGNH AG notice95 NH residentsauto-linked+1d
NOV 20CA AGCA AG noticeno count statedauto-linked+1d
NOV 25MA AGMA AG noticemost recent · 298 MA residentsauto-linked+6d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Aug 3, 2019 – Aug 27, 2019
Discovered: Sep 4, 2019· 32d undetected
Data types: Financial account · Identity (basic) · Government ID · PII
Attack vector: Phishing

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

MA298

NH95

MT15

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

6 days

Cadence

~1 / 2d

vs. multi-state median

1.3× 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.