DisclosureLens
UnknownLow

Bluemercury, Inc.

bd_2642f08b1384fa7f · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 28, 2016

Filed

Mar 10, 2017

To disclose

15 weeks

Affected

Not disclosed

Linked

2 filings

Confidence

95%
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.

Incident timeline

undetected · 301 days
discovery → filing · 15 weeks / 102 days

Feb 1, 2016

Begins

Nov 28, 2016

Discovered

Mar 10, 2017

Filed

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

Filing propagation · 2 filings · 2 states

View merged incident ↗
Montana State AGFeb 23 · first
Oregon State AG+15d · this page

Pattern: first filing Feb 23 (MT), last Mar 10 (OR) — a 15-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.