Rea.deeming Beauty, Inc.
ent_c3c0fa15edb84d3d86b24184
Disclosures
4
State AG · 4 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
18,133
nationwide · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Rea.deeming Beauty, Inc.
- Normalized
- readeeming beauty— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- New Hampshire State AGas victim2018-01-05
Rea.deeming Beauty, Inc. (dba beautyblender) notified NH AG of a data event affecting 58 NH residents. Malicious code on the website collected payment card info (name, address, full CC#, exp, CVV) between April 2015 and Oct 2026. Discovered Oct 26, 2017 by hosting provider. Forensic investigation confirmed data collection. Incident contained; additional security measures implemented.
- Massachusetts State AGas victim2018-01-05
Rea.deeming Beauty, Inc. d/b/a Beauty Blender reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2018-01-05. 350 Massachusetts residents were affected. The report records the breach type as electronic.
- Oregon State AGas victim2018-01-05
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.
- California State AGas victim2018-01-05
Rea.deeming Beauty Inc. (dba beautyblender) experienced a data breach involving malicious code (skimmer) on its website that collected payment card information. The malware was discovered on October 26, 2017, and confirmed to be present as of July 28, 2017. Due to lack of backups, the potential occurrence window is April 23, 2015, to October 26, 2017. 3,673 California residents were affected. The company removed the code, engaged forensic investigators, and notified regulators.