Confirmed breach. Intrusion Sep 19, 2022, discovered Dec 14, 2023 — the first regulatory filing landed 7 days later. 1 individuals reported across the linked filings.
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.
Regulatory clocksMaine✓ ME AG ≤30d · 7dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Government ID
Jurisdictions
2
ME VT
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Sep 19, 2022
When the intrusion reportedly occurred, per the linked filings
451 days
Breach discovered
Dec 14, 2023
Reported by MAINE AG filing
🍁Vermont State AGFirst filinglinked via multistate filing link · 100%
Security 1st Title notified consumers of a data breach involving unauthorized access to personal information. Affected data included names, addresses, and government IDs. The company offered complimentary credit monitoring and established a toll-free response line. The incident is contained.
Security 1st Title, LLC reported a data breach to the Maine Attorney General, discovered on December 14, 2023. The breach occurred on September 19, 2022, and was identified as an external system hacking event. One Maine resident was affected, with their name and Social Security number being compromised. In response, the company provided notification to the affected individual on December 21, 2023, and offered 12 months of complimentary credit monitoring services through IDX.
Affected (this filing): 1
ME AG ≤30d · 7d
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.