DisclosureLens
State AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 6 filings

Accounting & Tax Associates, Inc. — May 2025 breach

Clustered 6 filings across 5 jurisdictions · filing window May 23, 2025 Jul 21, 2025. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

not comparable

First → last filing

May 23, 2025 Jul 21, 2025

Merge confidence

100%

incident inc_f89ac056d2af41eb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe hacking. Intrusion May 14, 2025, discovered May 14, 2025 — the first regulatory filing landed 9 days later. Data reported: Government ID, Financial account, and Identity (basic). Notifications rolled out on a 59-day schedule across 6 filings beginning May 23, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
9days

Discovered → first regulatory filing

Discovery variance
49days

Range of discovered_at dates across filings

Filing span
59days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMassachusetts MA credit monitoring dueDate basis Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 14, 2025breach begins
May 14, 2025discovered · members disagree
notification delay · 9 days
May 23, 2025first filing
Jul 21, 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

  1. MAY 23MA AGMA AG noticefirst filing · 4,739 MA residentsday 0
  2. JUL 18MA AGMA AG notice4,464 MA residents+56d
  3. JUL 18NE AGNE AG noticeno count stated+56d
  4. JUL 18IN AGIN AG noticestates nationwide total 5,215+56d
  5. JUL 18ME AGME AG noticestates nationwide total 5,215+56d
  6. JUL 21NH AGNH AG noticemost recent · 24 NH residents+59d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 14, 2025
NE AG
Discovered
May 14, 2025NE AGJun 11, 2025NH AGJul 2, 2025ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
MA AG + ME AG + NH AG +1
Attack vector
Third-Party / Supply Chain
NE 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)

5,215

Sum of filed state slices

4,780· 91.7% of stated

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

US5,215
MA4,739
NH24
ME14
IN3

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

59 days

Cadence

~1 / 11.8d

vs. multi-state median

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