DisclosureLens
State AGConfirmed4 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 4 filings

L.A. Tax Service, LLP — June 2020 breach

Clustered 4 filings across 4 jurisdictions · filing window Oct 30, 2020 Nov 13, 2020. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

4 filings

States

4

Affected · reported

2,604

First → last filing

Oct 30, 2020 Nov 13, 2020

Merge confidence

100%

incident inc_961a1c90da5348aa · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings. Intrusion Jun 1, 2020–Sep 30, 2020, discovered Sep 15, 2020 — the first regulatory filing landed 45 days later. 2,604 individuals reported across the linked filings. Data reported: Government ID, Financial account, PII, and 2 more. Notifications rolled out on a 14-day schedule across 4 filings beginning Oct 30, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
45days

Discovered → first regulatory filing

Filing span
14days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delayno 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

Jun 1, 2020breach begins
Sep 15, 2020discovered
notification delay · 45 days
Oct 30, 2020first filing
Nov 13, 2020most 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. OCT 30MA AGMA AG noticefirst filing · 13 MA residentsday 0
  2. OCT 30CA AGCA AG noticestates nationwide total 50day 0
  3. OCT 30NH AGNH AG noticestates nationwide total 2,604day 0
  4. NOV 13IN AGIN AG noticemost recent · states nationwide total 2,604+14d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 10, 2020Sep 9, 2020
CA AG
Discovered
Sep 15, 2020· 97d undetected
NH AG
Data types
Financial · Financial account · Identity (basic) · Government ID · PII
MA AG + CA AG + NH AG
Attack vector
Unauthorized Access
CA AG

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

2,604

Sum of filed state slices

17· 0.7% of stated

99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US2,604
MA13
NH2
IN2

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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

14 days

Cadence

~1 / 4.7d

vs. multi-state median

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