UnknownMedium
Manduka
bd_5ecb4e4d561a06bf · schema v1 · pii pii-v1
Full breach record for Manduka →Manduka reported a data breach to the Oregon Attorney General. The breach was reported on 2018-03-27. The breach occurred during 2/22/2017 - 3/5/2018. The breach was discovered on 2/25/2018. 64,270 individuals were affected. Notice was sent on 3/26/2018.
Oregon clock✓ OR AG ≤45d4 weeks discovery → filing
⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
This filing is one of 5 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- bd_459f89eec1979764Washington State AGfiled 2018-03-27Verified
- bd_7ff02f57c5673209California State AGfiled 2018-03-27Verified
- bd_900e824b2ddbde8dMontana State AGfiled 2018-03-26(1d gap)Candidate
- bd_197f9054f6cba465California State AGfiled 2018-06-08(73d gap)Verified
Source provenance
- Source URL
- https://justice.oregon.gov/consumer/DataBreach/
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
- f96165ec3046f4dd68fbca9febf6a8887de58a9288ca0b12dedd164ddae8e89c
Reporting entity
- Name
- Mandukanorm: manduka
Victim entity
- Name
- Mandukanorm: manduka
Incident
- Discovered
- Feb 25, 2018
- Materiality determined
- —
- Notification sent
- Mar 26, 2018
- Affected individuals
- 64,270
- Data types
- —
- Attack vector
- Unknown
- Threat actor
- External
Compliance
- Time to disclose
- 4 weeks(30 days from discovery to filing)
- Compliance flags
- OR AG ≤45d
- Discovery-date grounding
- AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
Extraction provenance
- Status
- No extraction artifact recorded for this disclosure.