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

Confirmed2 filings · 2 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 2 filings

Moore, Ellison & McDuffie, CPAs, PA — October 2024 breach

Clustered 2 filings across 2 jurisdictions · filing window Feb 21, 2025 → Feb 22, 2025. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 filings

States

Affected · reported

First → last filing

Feb 21, 2025 → Feb 22, 2025

Merge confidence

100%

incident inc_a0ddb0c143284ff4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. Intrusion Oct 25, 2024–Oct 30, 2024, discovered Jan 16, 2025 — the first regulatory filing landed 36 days later. 3 individuals reported across the linked filings. Data reported: Government ID. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

36days

Discovered → first regulatory filing

Filing span

1days

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.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 25, 2024breach begins

Jan 16, 2025discovered

notification delay · 36 days

Feb 21, 2025first filing

Feb 22, 2025most recent filing

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

Member cascade — every filing about this breach

FEB 21NE AGNE AG noticefirst filing · no count statedauto-linkedday 0
FEB 22MA AGMA AG noticemost recent · 3 MA residents+1d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Oct 25, 2024 – Oct 30, 2024
Discovered: Jan 16, 2025· 83d undetected
Data types: Government ID

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

1 days

vs. multi-state median

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