DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed2 records · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedailockhigh sensitivity
Merged incident · 2 records

MORGAN SERVICES, INC.

Clustered 2 records across 1 jurisdiction: 1 filing and 1 leak-site claim · filed Oct 1, 2026. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 records

States

1

Affected · reported

213

First → last filing

Oct 1, 2026

Merge confidence

100%

incident inc_7c0e6adeea104d27 · merged by deterministic · confidence 100%

Confirmed breach. 213 individuals reported across the linked filings. Data reported: Government ID and Identity (basic).

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

identity_government

Incident timeline

? — ?breach window unknown
Oct 1, 2026first & only filing
—watching for filings

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing and leak-site claim in this incident

  1. AUG 26Leak siteailock postfirst record · attacker claim · unverifiedday 0
  2. OCT 1MA AGMA AG noticemost recent · 213 MA residents+36d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
—
Data types
Identity (basic) · Government ID
MA AG

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

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.

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.