Clustered 3 filings across 3 jurisdictions · filing window Jul 18, 2023 → Aug 31, 2023. View entity profile → Other incidents for this victim →
incident inc_f4358e129602465f · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta — needs two dated filings.
FEDERAL WA
Leak Site · SEC 8-K · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jul 11, 2023
Reported by WASHINGTON AG filing
Jul 18, 2023
Registrant determined the incident material — starts the SEC 4-business-day clock
The Estée Lauder Companies Inc. is an American multinational cosmetics company, a manufacturer and marketer of makeup, skincare, fragrance and hair care products, based in Midtown Manhattan, New York City. It is the second largest cosmetics company in the world after L'Oréal.
The Estée Lauder Companies Inc. filed an 8-K on July 18, 2023, reporting a cybersecurity incident via an attached press release. The filing does not provide specific details regarding the nature of the incident, data types affected, or number of individuals impacted.
The Estée Lauder Companies Inc., a business sector entity reported a other incident to the Washington Attorney General. The organization became aware of the incident on 2023-07-11 and filed notice on 2023-08-31. 150,535 Washington residents were affected. 51 days elapsed between awareness and notification. 0 days to identify the breach. 40 days to contain the breach.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 150,535