GLOBALClaimed by DarkSideFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Feb 1, 2021bd_51f22e2136e6dd46
Clustered 3 filings across 3 jurisdictions · filing window Feb 1, 2021 → Jul 9, 2021. View entity profile → Other incidents for this victim →
incident inc_5aeb9bf878524652 · 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) · Financial account
CA ME
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 2, 2021 → Feb 23, 2021
When the intrusion reportedly occurred, per the linked filings
May 26, 2021
Reported by MAINE AG filing
Guess?, Inc. reported an external system breach (hacking) occurring between February 2 and 23, 2021, discovered on May 26, 2021. The incident affected 1,304 individuals, including 4 Maine residents. Compromised data included names and financial account or credit/debit card numbers (with security codes/PINs). The company provided written notification on July 9, 2021, and offered one year of credit monitoring and identity theft protection services via Experian.
Guess?, Inc. experienced a ransomware incident between February 2 and February 23, 2021, involving unauthorized access and an attempt to encrypt systems. Personal information including names, SSNs, driver's license numbers, passport numbers, and financial account numbers may have been accessed. The company engaged forensic investigators, notified law enforcement, and offered credit monitoring 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): 1,304