Confirmed breach. Intrusion Apr 10, 2023, discovered Apr 10, 2023 — the first regulatory filing landed 129 days later (flagged late). 6 individuals reported across the linked filings.
ICAFS, Inc. dba General Services Corporation notified consumers of a cybersecurity incident discovered on April 10, 2023, involving unauthorized access to personal information including names and government identifiers. The company disabled systems, engaged third-party specialists, notified law enforcement, and offered credit monitoring. No evidence of misuse was found.
VT AG >45 bday
42 days
⛰️New Hampshire State AGlinked via multistate filing link · 95%
General Services Corporation (GSC) reported a cyber attack on April 10, 2023, affecting approximately 6 New Hampshire residents. GSC engaged third-party specialists, notified law enforcement, and rotated credentials. Notifications were sent starting July 6, 2023, offering credit monitoring. The attack involved unauthorized access to network data, potentially including personal identification information.
Affected (this filing): 6
🦞Maine State AGMost recentlinked via multistate filing link · 95%
ICAFS, Inc. dba General Services Corporation (“GSC”) reported an external system breach (hacking) that occurred on April 10, 2023, and was discovered on May 30, 2023. The breach affected 9,913 individuals in total, including 6 Maine residents. The compromised information includes names in combination with Driver's License or Non-Driver Identification Card Numbers. GSC began notifying affected consumers on July 6, 2023, and offered 24 months of credit monitoring and identity protection services through IDX.
Affected (this filing): 6
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.