HackingRetail & ConsumerRetailStolen CredentialsCapture Stored DataData ExfiltratedCustomer Data InvolvedFinancial accountIdentity (basic)LowResolved

Pie Five Pizza

bd_3839eb8a82ca8167 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Apr 5, 2019

To disclose

—

Affected

Not disclosed

Linked

4 filings

Confidence

65%

Full breach record for Pie Five Pizza →

Pie Five Pizza notified customers of a security incident where an unauthorized individual installed malicious software on payment processing systems to capture payment card data. The incident affected transactions between September 6, 2018, and December 2, 2018, at certain locations. No SSNs or other sensitive PII were compromised. Pie Five Pizza engaged forensic experts and alerted law enforcement.

J jump to incidentP pin to compareR raw source

Incident timeline

Sep 6, 2018

Begins

Apr 5, 2019

Filed

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

Linked disclosures

Why this link?

Regulatory filings (3) · sorted by filing gap

California State AGbd_a3716737fdc8bd6e2019-04-05Verified
New Hampshire State AGbd_a2ba8bef43da6f092019-04-15 · +10dVerified
Delaware State AGbd_fe5e609a57c12dcc2019-06-01 · +57dVerified

Name: Pie Five Pizza
norm: pie five pizza
Domain: piefivepizza.com

Name: Pie Five Pizza
norm: pie five pizza
Domain: piefivepizza.com
Industry: Retail & Consumerllm

Discovered: —
Breach occurred: Sep 6, 2018 – Dec 2, 2018
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Financial accountIdentity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1056 Input CaptureT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Initial access: valid_credentials

During the incident: Initiating an internal review
Engaging independent forensic experts to assist us in the investigation and remediation of our systems
Alerting law enforcement
Changes made: Review and enhance our security measures moving forward
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

California State AGApr 5 · first

Montana State AGApr 5 · first · this page

New Hampshire State AG+10d

Delaware State AG+57d

Pattern: first filing Apr 5 (CA), last Jun 1 (DE) — a 57-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/OCP/CON-Sample-Notice.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 5, 2019
Raw hash: 575daaa98440c09ffebc89aca3e2cc242a9551cf457c9b254cc34b7c83b8fe3a

Linked disclosures

Regulatory filings (3) · sorted by filing gap

Reporting entityPie Five Pizza

Victim entityPie Five Pizza

IncidentUnauthorized Access

Stated responseInitiating an internal review

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov