DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed5 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

INTUIT INC. — June 2023 breach

Clustered 5 filings across 3 jurisdictions · filing window Mar 15, 2024 → May 1, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

not comparable

First → last filing

Mar 15, 2024 → May 1, 2024

Merge confidence

100%

incident inc_bde445ce9fb141f1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Jun 4, 2023–Feb 21, 2024, discovered Feb 27, 2024 — the first regulatory filing landed 17 days later. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 47-day schedule across 5 filings beginning Mar 15, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
17days

Discovered → first regulatory filing

Discovery variance
35days

Range of discovered_at dates across filings

Filing span
47days

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 clocksMaine✓ ME AG ≤30d · 17dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 4, 2023breach begins
Feb 27, 2024discovered · members disagree
notification delay · 17 days
Mar 15, 2024first filing
May 1, 2024most 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. MAR 15IN AGIN AG noticefirst filing · 4 IN residentsday 0
  2. MAR 15ME AGME AG notice1 ME residentsday 0
  3. MAY 1MA AGMA AG notice5 MA residents+47d
  4. MAY 1ME AGME AG notice1 ME residents+47d
  5. MAY 1IN AGIN AG noticemost recent · 2 IN residents+47d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 4, 2023
IN AG
Discovered
Feb 27, 2024ME AGApr 2, 2024ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID
ME AG + MA AG
Attack vector
Unauthorized Access
ME AG

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

MA5
IN4
ME1

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

47 days

Cadence

~1 / 11.8d

vs. multi-state median

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