Clustered 2 filings across 2 jurisdictions · filing window Aug 8, 2025 → Aug 11, 2025. View entity profile → Other incidents for this victim →
incident inc_34af47446df347f7 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic)
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 NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 2, 2025
When the intrusion reportedly occurred, per the linked filings
May 7, 2025
Reported by MAINE AG, NEW HAMPSHIRE AG filings
Value Store It Management Inc. identified an external system breach on May 7, 2025, which initially occurred on May 2, 2025. The breach impacted 2 Maine residents, who were notified on August 8, 2025. The company offered affected individuals 12 to 24 months of credit monitoring services through TransUnion Cyberscout.
Affected (this filing): 2
Value Store It Management, Inc. (VSI) notified the New Hampshire Attorney General's Office on August 8, 2025, of a cybersecurity incident affecting approximately 3 New Hampshire residents. On or about May 7, 2025, an unauthorized party accessed VSI's internal network. A forensic investigation revealed that files containing personal information—including names, dates of birth, driver's license numbers, financial account information, and potentially Social Security numbers—were potentially accessed. VSI contained the incident, engaged cybersecurity experts, and provided affected individuals with credit monitoring services and guidance on fraud alerts.
Affected (this filing): 3
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.