Clustered 2 filings across 2 jurisdictions · filed Jun 5, 2026. View entity profile → Other incidents for this victim →
incident inc_da04212e08a345f9 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA ME
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 17, 2026 → May 31, 2026
When the intrusion reportedly occurred, per the linked filings
May 31, 2026
Reported by MAINE AG filing
Meta Platforms, Inc. filed a data breach notification with the California Attorney General. The breach occurred between April 17, 2026, and May 31, 2026. The filing provides only the organization name and breach dates; no details regarding the nature of the incident, data types affected, or number of individuals impacted are disclosed in this record.
Meta Platforms, Inc. reported a cybersecurity incident to the Maine Attorney General. The breach occurred on April 17, 2026, and was discovered on May 31, 2026. The incident affected a total of 20,225 individuals, including 30 Maine residents. The specific nature of the breach and data types acquired were not explicitly detailed in the filing, categorized broadly as 'Other'. Electronic notification was sent to affected consumers, but no identity theft protection services were offered.
Affected (this filing): 20,225
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.