HackingRetail & ConsumerRetailVulnerability ExploitCapture Stored DataTargetedIdentity (basic)Financial accountFinancial credentialsLowContained

Simon Pearce Inc

bd_e340f93c3dbb075c · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 28, 2019

Filed

May 7, 2019

To disclose

6 weeks

Affected

2state residents only

Linked

3 filings

Confidence

67%

Full breach record for Simon Pearce Inc →

Simon Pearce Inc notified customers of a cybersecurity incident where an unauthorized third party illegally placed computer code on its e-commerce system. The incident, discovered on March 28, 2019, compromised names, addresses, and credit/debit card information including CVV codes. No SSN or driver's license data was impacted. The company engaged forensic investigators and notified law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 6 weeks / 40 days

Mar 28, 2019

Discovered

May 7, 2019

Filed

vs. sector median

2 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Massachusetts State AGbd_62dd82d11467c1892019-05-07Verified
New Hampshire State AGbd_6dedd4cd2a438e062019-05-08 · +1dVerified

Name: Simon Pearce Inc
norm: simon pearce

Name: Simon Pearce Inc
norm: simon pearce
Industry: Retail & Consumerllm

Discovered: Mar 28, 2019
Materiality determined: —
Notification sent: —
Affected individuals: 2state-resident count only
Data types: Identity (basic)Financial accountFinancial credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input Capture
Threat actor: ExternalFinancial
Regulator citations: notified law enforcement
Initial access: exploit_public_facing

During the incident: Hired a forensic security firm to investigate the incident
Notified law enforcement
Removed the code from our website
Alerted the credit card brands of the incident
Taken additional technical steps to secure our website
Changes made: Taken additional technical steps to secure our website and prevent this type of incident from occurring in the future
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Massachusetts State AGMay 7 · first

Montana State AGMay 7 · first · this page

New Hampshire State AG+1d

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/OCP/CON-Simon-Pearce-Notification-Template-c.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 7, 2019
Raw hash: 06113673e396e94759da45fd8d91dfd8eac0320ef4cf7ff0a251b24b98493df3

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entitySimon Pearce Inc

Victim entitySimon Pearce Inc

Incidentdiscovered Mar 28, 2019

Stated responseHired a forensic security firm to investigate the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov