Clustered 2 filings across 2 jurisdictions · filed Jan 19, 2023. View entity profile → Other incidents for this victim →
incident inc_f9d52cfa0e6d4975 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Financial account
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 26, 2022
When the intrusion reportedly occurred, per the linked filings
Sep 26, 2022
Reported by VERMONT AG, MAINE AG filings
Digital Prospectors Corp. notified consumers of a data breach affecting a single employee laptop discovered on September 26, 2022. An unknown actor briefly accessed files containing names and other personal information. No actual misuse was confirmed. The company offered 24 months of credit monitoring and identity restoration services to affected individuals.
Digital Prospectors Corp. experienced an external system breach on September 26, 2022, which was also the date of discovery. The breach affected 7 Maine residents, and a total of 553 individuals. The compromised information included names or other personal identifiers in combination with financial account numbers or credit/debit card numbers, along with their security codes, access codes, passwords, or PINs. The company provided written notification to the affected consumers on January 19, 2023, and offered two years of credit monitoring and identity restoration services through Cyberscout.
Affected (this filing): 7
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.