DisclosureLens
MalwareRetail & ConsumerRetailRansomwareRansom DemandedRansom PaidData EncryptedCustomer Data InvolvedIdentity (basic)Financial accountLowResolved

Roxy Trading, Inc.

bd_afef98de77484193 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Feb 28, 2017

To disclose

—

Affected

3state residents only

Linked

2 filings

Confidence

66%
Full breach record for Roxy Trading, Inc. →

Roxy Trading, Inc. (parent of Chimes) experienced a ransomware attack on January 22, 2017, where a hacker gained access to a server and encrypted files. A password-protected file containing customer payment information (names, business addresses, phone numbers, emails, credit card numbers) was among those affected. The company paid the ransom to restore access. Investigation found no evidence of data exfiltration. Three New Hampshire residents were affected. Notices were sent on February 22, 2017, offering one year of identity protection services.

Incident timeline

Jan 22, 2017

Begins

Feb 28, 2017

Filed

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

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

Filing propagation · 2 filings · 2 states

View merged incident ↗
Montana State AGFeb 22 · first
New Hampshire State AG+6d · this page

Pattern: first filing Feb 22 (MT), last Feb 28 (NH) — a 6-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.