MalwareRetail & ConsumerRetailData ExfiltratedCustomer Data InvolvedPCIFinancial accountFinancial credentialsIdentity (basic)LowContained

Manduka

bd_7ff02f57c5673209 · schema v1 · pii pii-v1

Severity

Low

Discovered

Feb 25, 2018

Filed

Mar 27, 2018

To disclose

4 weeks

Affected

Not disclosed

Linked

7 filings

Confidence

65%

Full breach record for Manduka →3 incidents on file

Manduka experienced a data security incident involving unauthorized malware installation on its e-commerce web platform. The incident occurred between February 22, 2017, and March 5, 2018, and was discovered on February 25, 2018. Customer payment card information, including names, card numbers, expiration dates, and security codes, may have been compromised. Manduka notified the FBI and Secret Service and retained a forensics firm to investigate.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 368 days

discovery → filing · 4 weeks / 30 days

Feb 22, 2017

Begins

Feb 25, 2018

Discovered

Mar 27, 2018

Filed

vs. sector median

3 wks faster

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

New Hampshire State AGbd_3e061c3e758c0dce2018-03-27Verified
Washington State AGbd_459f89eec19797642018-03-27Verified
Oregon State AGbd_5ecb4e4d561a06bf2018-03-27Verified
Montana State AGbd_900e824b2ddbde8d2018-03-26 · +1dCandidate

Show 2 more filings ↓up to 127d gap

California State AGbd_197f9054f6cba4652018-06-08 · +73dVerified
New Hampshire State AGbd_7e59e035c09ab18b2018-08-01 · +127dVerified

Name: Manduka
norm: manduka

Name: Manduka
norm: manduka
Industry: Retail & Consumerllm

Discovered: Feb 25, 2018
Breach occurred: Feb 22, 2017 – Mar 5, 2018
Undetected for: 368 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: PCIFinancial accountFinancial credentialsIdentity (basic)
Attack vector: Unknown
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Reported the incident to the Federal Bureau of Investigation (FBI)Working with both the FBI and the United States Secret Service

During the incident: Took immediate steps to secure this information
Contacted the appropriate law enforcement agencies
Launched an investigation
Retained a leading forensics firm to determine what happened
Reported the incident to the Federal Bureau of Investigation (FBI)
Working with both the FBI and the United States Secret Service
Reported the matter to the payment card brands
Changes made: Taken steps to enhance the security of Manduka customer information and our e-commerce web platform
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 4 weeks(30 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 · 5 states

View merged incident ↗

Montana State AGMar 26 · first

New Hampshire State AG+1d

Washington State AG+1d

Oregon State AG+1d

California State AG+1d · this page

California State AG+74d

New Hampshire State AG+128d

Pattern: first filing Mar 26 (MT), last Aug 1 (NH) — a 128-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://oag.ca.gov/ecrime/databreach/reports/sb24-134813
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 27, 2018
Raw hash: b26030a1fe5b17a9d8150a45daceedf54d1160de7cda6f536d39f909897fc72e

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityManduka

Victim entityManduka

Incidentdiscovered Feb 25, 2018

Stated responseTook immediate steps to secure this information

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov