AccidentalRetail & ConsumerRetailMisconfigurationCustomer Data InvolvedPIIPCIIdentity (basic)Financial accountLowResolved

Zulily, Inc.

bd_430b9bf43cf0ad63 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jun 26, 2022

Filed

Jul 22, 2022

To disclose

26 days

Affected

140state residents only

Linked

6 filings

Confidence

66%

Full breach record for Zulily, Inc. →

Zulily, LLC disclosed a misconfiguration incident where checkout code sent customer transaction data (including PCI data) to an unauthorized payment processor. The incident occurred between Feb 23 and June 15, 2022. Zulily discovered the issue on June 26, 2022, corrected the code, notified processors, and issued refunds for duplicate shipping charges.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 123 days

discovery → filing · 26 days

Feb 23, 2022

Begins

Jun 26, 2022

Discovered

Jul 22, 2022

Filed

vs. sector median

5 wks faster

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Maine State AGbd_3c2a0b3c2997f9b52022-07-22Candidate
Indiana State AGbd_70a151ad6b5eea7a2022-07-22Verified
Oregon State AGbd_d4316952ca18512e2022-07-22Verified
Massachusetts State AGbd_dfe6b17bfd4229d92022-07-22Verified

Show 1 more filing ↓

California State AGbd_ec59f3b17c8c3fe92022-07-22Verified

Name: Zulily, Inc.
norm: zulily

Name: Zulily, Inc.
norm: zulily
Industry: Retail & Consumerllm

Discovered: Jun 26, 2022
Breach occurred: Feb 23, 2022 – Jun 15, 2022
Undetected for: 123 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 140state-resident count only
Data types: PIIPCIIdentity (basic)Financial account
Attack vector: Misconfiguration
MITRE ATT&CK: T1190 Exploit Public-Facing Application

During the incident: Corrected the issue
Notified the payment processors
Processing a refund for those customers who were charged more than once for shipping and handling
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Maine State AGJul 22 · first

Indiana State AGJul 22 · first

Oregon State AGJul 22 · first

Massachusetts State AGJul 22 · first

California State AGJul 22 · first

Montana State AGJul 22 · 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://dojmt.gov/wp-content/uploads/OCP/Consumer-Notification-Letter-421.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 22, 2022
Raw hash: c21aaeaa6dca1b00fcae41c0c9dc153404f370266d74b2bf9a176af77d933814

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityZulily, Inc.

Victim entityZulily, Inc.

Incidentdiscovered Jun 26, 2022

Stated responseCorrected the issue

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov