Clustered 3 filings across 3 jurisdictions · filing window Nov 10, 2023 → Jun 7, 2024. View entity profile → Other incidents for this victim →
incident inc_df4d819c119f431b · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Identity (basic)
CA IN
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 12, 2023
When the intrusion reportedly occurred, per the linked filings
Oct 14, 2023
Reported by CALIFORNIA AG filing
Providing expert landscape maintenance, landscape construction and tree care services for commercial, municipal and homeowner associations.
Mariposa Landscapes Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-10-12 and was reported on 2024-06-07. 1 Indiana residents were affected. 8,131 individuals affected in total.
Mariposa Landscapes Inc. notified the California Attorney General of a data breach where an unauthorized actor accessed limited information between October 12 and October 15, 2023. The company discovered the incident on October 14, 2023, following a network disruption. Affected data may include first and last names in combination with other unspecified data elements. The company engaged third-party specialists, implemented additional technical safeguards, and is offering complimentary credit monitoring and identity protection services to affected individuals.
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): 8,131