Clustered 2 filings across 2 jurisdictions · filed Jan 5, 2018. View entity profile → Other incidents for this victim →
incident inc_8bc2aeda6c134264 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
CA OR
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 25, 2015 → Oct 26, 2017
When the intrusion reportedly occurred, per the linked filings
Oct 26, 2017
Reported by CALIFORNIA AG filing
Nov 27, 2017
Reported by OREGON AG filing
Rea.deeming Beauty, Inc. dba beautyblender reported a data breach to the Oregon Attorney General. The breach was reported on 2018-01-05. The breach occurred during 4/25/2015 - 10/26/2017. The breach was discovered on 11/27/2017. 18,133 individuals were affected. Notice was sent on 1/5/2018.
Affected (this filing): 18,133
Rea.deeming Beauty Inc. d/b/a beautyblender disclosed a data security incident where malware on its website collected customer payment card information (name, address, full credit card number, expiration, CVV). The malware was present between April 23, 2015, and October 26, 2017. 3,673 California residents were notified. The company removed the malware and implemented additional security measures.
Affected (this filing): 3,673
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.