DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 records · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 10 records

THE ESTEE LAUDER COMPANIES INC. — August 2025 breach

Clustered 10 records across 9 jurisdictions: 9 filings and 1 leak-site claim · filing window Jul 10, 2026 → Jul 21, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 records

States

9

Affected · reported

31,859

First → last dated filing

Jul 10, 2026 → Jul 21, 2026

Merge confidence

100%

incident inc_f62c8ed04bc74a64 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 9, 2025–Aug 12, 2025, discovered Jun 19, 2026. 31,859 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 5 more. Notifications rolled out on a 11-day schedule across 7 dated filings beginning Jul 10, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
11days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 9, 2025breach begins
Jun 19, 2026discovered
Jul 10, 2026first dated filing
Jul 21, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

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

  1. NOV 21Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  2. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  3. JUL 10VT AGVT AG notice7 VT residents+230d
  4. JUL 17NE AGNE AG noticefiling day not on record · no count stated—
  5. JUL 17IN AGIN AG noticestates nationwide total 31,859+237d
  6. JUL 17CA AGCA AG noticeno count stated+237d
  7. JUL 17WA AGWA AG notice2,110 WA residents+237d
  8. JUL 17MA AGMA AG notice336 MA residents+237d
  9. JUL 20NH AGNH AG notice72 NH residents+240d
  10. JUL 21TX AGTX AG noticemost recent · states nationwide total 31,859+241d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 9, 2025
NE AG
Discovered
Jun 19, 2026· 314d undetected
IL AG + WA AG + MA AG +1
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
IL AG + VT AG + NE AG +5
Attack vector
Unauthorized Access
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)

31,859

Sum of filed state slices

4,640· 14.6% of stated

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

US31,859
WA2,110
TX1,959
MA336
IN156
NH72
VT7

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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

11 days

Cadence

~1 / 1.8d

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.