Quest Nutrition reported a data breach to the Montana Attorney General. The breach was reported on 2018-09-28. The breach occurred on 11/10/2017. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Sep 28, 2018. View entity profile → Other incidents for this victim →
incident inc_ed5c3826d52e465f · merge_method deterministic · confidence 100%
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 10, 2017
When the intrusion reportedly occurred, per the linked filings
Quest Nutrition reported a data breach to the Montana Attorney General. The breach was reported on 2018-09-28. The breach occurred on 11/10/2017. 1 Montana residents were affected.
Affected (this filing): 1
Quest Nutrition reported a data breach involving an employee email account. An external actor sent phishing emails to employees soliciting login credentials. The actor used these credentials to access the email account, which contained personal information of employees, influencers, and partners. Affected data may include names, addresses, usernames, passwords, driver's license numbers, health insurance information, financial account information, and Social Security numbers. Quest Nutrition reset passwords, implemented additional email security tools, and offered one year of identity protection services.
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.