MalwareRetail & ConsumerRetailRansomwareData EncryptedCustomer Data InvolvedIdentity (basic)Government IDFinancial accountMediumContained

GUESS?, LLC

bd_d16da922327a3ecd · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jul 9, 2021

To disclose

—

Affected

Not disclosed

Linked

6 filings

Confidence

65%

Full breach record for GUESS?, LLC →

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.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >90d

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline

Feb 2, 2021

Begins

Jul 9, 2021

Filed

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitedarksidebd_51f22e2136e6dd462021-02-01 · +158dVerified by operator

Regulatory filings (4) · sorted by filing gap

Indiana State AGbd_bc1b7eef14b508172021-07-09Verified by operator
Maine State AGbd_c316604e1deedfda2021-07-09Verified
New Hampshire State AGbd_e514d0f72546771c2021-07-09Verified
Massachusetts State AGbd_f799a3576eecd77c2021-07-09Verified by operator

Name: GUESS?, LLC
norm: guess

Name: GUESS?, LLC
norm: guess
Industry: Retail & Consumerllm

Discovered: —
Breach occurred: Feb 2, 2021 – Feb 23, 2021
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)Government IDFinancial account
Data elements: Social Security number
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1078 Valid Accounts
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcement

During the incident: Activated our incident response plan
Took measures to stop the access
Launched an investigation
Engaged a cybersecurity forensic firm to assist with the investigation
Notified law enforcement and are cooperating with their investigation
Implemented additional measures to enhance our security protocols
Offering a complimentary one-year membership in Experian’s IdentityWorks Credit 3B
Changes made: Implemented additional measures to enhance our security protocols
Source: Quoted from the filing itself, not independently verified.

Compliance flags: Leak >90d
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Indiana State AGJul 9 · first

Maine State AGJul 9 · first

New Hampshire State AGJul 9 · first

Massachusetts State AGJul 9 · first

California State AGJul 9 · first · this page

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-542711
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 9, 2021
Raw hash: 06c404fadfe135d031452c9998fd27bdfdd1a8d45f55d4777c82a2d40c61a3bd

Linked disclosures

Ransomware claims (1)

Regulatory filings (4) · sorted by filing gap

Reporting entityGUESS?, LLC

Victim entityGUESS?, LLC

IncidentRansomware

Stated responseActivated our incident response plan

ComplianceLeak >90d

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov