HackingRetail & ConsumerRetailStolen CredentialsData ExfiltratedCustomer Data InvolvedPIIIdentity (basic)Financial accountLowContained

Shoe Sensation

bd_c196a41f43f20a2b · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 5, 2024

Filed

Feb 21, 2025

To disclose

11 weeks

Affected

19state residents only

Linked

7 filings

Confidence

66%

Full breach record for Shoe Sensation →2 incidents on file

Shoe Sensation, Inc. notified customers of a data breach occurring in August 2024 and discovered in December 2024. Unauthorized access exposed customer names, addresses, and credit card numbers. The company took the website offline, removed compromised code, applied security patches, and engaged Kroll to provide identity monitoring services to affected individuals.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 126 days

discovery → filing · 11 weeks / 78 days

Aug 1, 2024

Begins

Dec 5, 2024

Discovered

Feb 21, 2025

Filed

vs. sector median

+4 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Nebraska State AGbd_2d3517160cd7b51e2025-02-21Verified
New Hampshire State AGbd_80668201a3a71c292025-02-21Verified
Maryland State AGbd_8bec2d3825d64ae22025-02-20 · +1dCandidate
Maine State AGbd_2c262b7659012c112025-02-24 · +3dVerified

Show 2 more filings ↓up to 11d gap

Vermont State AGbd_4295b53a572ceb362025-02-27 · +6dVerified
Massachusetts State AGbd_b84c36a063a5acb12025-03-04 · +11dVerified

Name: Shoe Sensation
norm: shoe sensation

Name: Shoe Sensation
norm: shoe sensation
Industry: Retail & Consumerllm

Discovered: Dec 5, 2024
Breach occurred: Aug 1, 2024
Undetected for: 126 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 19state-resident count only
Data types: PIIIdentity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Initial access: exploit_public_facing

During the incident: Took our website offline to prevent further unauthorized access
Conducted a comprehensive end-to-end review of the code ensuring that all the compromised code was removed
Applied all relevant security patches to fortify the website
Reached out to our provider for additional support and guidance
Secured the services of Kroll to provide identity monitoring
Changes made: Applied all relevant security patches to fortify the website
Conducted a comprehensive end-to-end review of the code ensuring that all the compromised code was removed
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 11 weeks(78 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

Maryland State AGFeb 20 · first

Nebraska State AG+1d

New Hampshire State AG+1d

Montana State AG+1d · this page

Maine State AG+4d

Vermont State AG+7d

Massachusetts State AG+12d

Pattern: first filing Feb 20 (MD), last Mar 4 (MA) — a 12-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

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://dojmt.gov/wp-content/uploads/2025/03/Consumer-notification-letter-176.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 21, 2025
Raw hash: 14b7c67d228675545513f5e00fdfc947155744737ceca7c684428daba5e21f16

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityShoe Sensation

Victim entityShoe Sensation

Incidentdiscovered Dec 5, 2024

Stated responseTook our website offline to prevent further unauthorized access

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov