UnknownLow
Bluemercury, Inc.
bd_2642f08b1384fa7f · schema v1 · pii pii-v1
Full breach record for Bluemercury, Inc. →Bluemercury, inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2017-03-10. The breach occurred during 2/1/2016 - 12/31/2016. The breach was discovered on 11/28/2016. Notice was sent on 2/23/2017.
Oregon clock✗ OR AG >45d15 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 2 about the same incident.View merged incident
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- bd_5ba2a1d8aff2e354Montana State AGfiled 2017-02-23(15d gap)Candidate
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 10, 2017
- Raw hash
- df3f50ddfb1a55c15317d92fd6369cc671f6ea74ec293b07d213a11227ac5133
Reporting entity
- Name
- Bluemercury, Inc.norm: bluemercury
Victim entity
- Name
- Bluemercury, Inc.norm: bluemercury
Incident
- Discovered
- Nov 28, 2016
- Materiality determined
- —
- Notification sent
- Feb 23, 2017
- Affected individuals
- Not disclosed
- Data types
- —
- Attack vector
- Unknown
- Threat actor
- External
Compliance
- Time to disclose
- 15 weeks(102 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.