HackingRetail & ConsumerRetailStolen CredentialsTargetedIdentity (basic)Financial accountLowContained

Makeup Geek, LLC

bd_5bb819488548ab96 · schema v1 · pii pii-v1

Severity

Low

Discovered

Dec 18, 2017

Filed

Feb 8, 2018

To disclose

7 weeks

Affected

7state residents only

Linked

2 filings

Confidence

65%

Full breach record for Makeup Geek, LLC →3 incidents on file

Makeup Geek, LLC notified customers of a data breach where malicious code was inserted into its website between Dec 4-19, 2017, intercepting names, addresses, and credit/debit card info. The company engaged forensic investigators, removed the code, and implemented additional security measures.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 14 days

discovery → filing · 7 weeks / 52 days

Dec 4, 2017

Begins

Dec 18, 2017

Discovered

Feb 8, 2018

Filed

vs. sector median

on median

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

New Hampshire State AGbd_f282d7e60834f2c22018-01-19 · +20dVerified

Name: Makeup Geek, LLC
norm: makeup geek
Domain: makeupgeek.com

Name: Makeup Geek, LLC
norm: makeup geek
Domain: makeupgeek.com
Industry: Retail & Consumerllm

Discovered: Dec 18, 2017
Breach occurred: Dec 4, 2017 – Dec 19, 2017
Undetected for: 14 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 29, 2018
Affected individuals: 7state-resident count only
Data types: Identity (basic)Financial account
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1056 Input Capture
Threat actor: ExternalFinancial
Regulator citations: Notifying required state regulators
Initial access: exploit_public_facing

During the incident: Brought in an outside cybersecurity firm to investigate
Removed the malicious code
Implemented additional security measures to prevent future similar incidents
Notifying required state regulators and credit reporting agencies
Changes made: Enhancing security procedures and practices to minimize the risk of such an event reoccurring
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 7 weeks(52 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

New Hampshire State AGJan 19 · first

Montana State AG+20d · this page

Pattern: first filing Jan 19 (NH), last Feb 8 (MT) — a 20-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.

Source URL: https://dojmt.gov/wp-content/uploads/Makeup-Geek-LLC.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 8, 2018
Raw hash: 6bfd6f26d9cdba737123085f7d50b41fe7ccec20784608dbaa6f3ad4c0bfdeb7

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityMakeup Geek, LLC

Victim entityMakeup Geek, LLC

Incidentdiscovered Dec 18, 2017

Stated responseBrought in an outside cybersecurity firm to investigate

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov