Manduka
bd_197f9054f6cba465 · schema v1 · pii pii-v1
Full breach record for Manduka →3 incidents on fileManduka experienced a data security incident involving unauthorized malware installation on its e-commerce platform. Payment card information (names, card numbers, expiration dates, security codes) for customers who used the platform between February 22, 2017, and May 20, 2018, was potentially compromised. The incident was discovered on February 25, 2018, with a second malware reinstallation detected in May 2018. Manduka engaged forensic investigators, notified law enforcement (FBI, Secret Service), and implemented remediation measures including MFA and platform migration. 9,651 California residents were notified.
J jump to incidentP pin to compareR raw source
Incident timeline
Feb 22, 2017
Begins
Feb 25, 2018
Discovered
Jun 8, 2018
Filed
vs. sector median
+7 wks slower
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- New Hampshire State AGbd_7e59e035c09ab18b2018-08-01 · +54dVerified
- New Hampshire State AGbd_3e061c3e758c0dce2018-03-27 · +73dVerified
- Washington State AGbd_459f89eec19797642018-03-27 · +73dVerified
- Oregon State AGbd_5ecb4e4d561a06bf2018-03-27 · +73dVerified
Show 2 more filings ↓Show fewer ↑up to 74d gap
- California State AGbd_7ff02f57c56732092018-03-27 · +73dVerified
- Montana State AGbd_900e824b2ddbde8d2018-03-26 · +74dCandidate
Filing propagation · 7 filings · 5 states
View merged incident ↗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
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.