Pet Food Experts, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-30. The breach occurred from 5/1/2022 to 5/3/2022. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Jun 30, 2022. View entity profile → Other incidents for this victim →
incident inc_358aa32fd7054db0 · merge_method llm · confidence 44%
Discovered → first regulatory filing
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.
Identity (basic) · Government ID
ME MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 1, 2022
When the intrusion reportedly occurred, per the linked filings
Jun 3, 2022
Reported by MAINE AG filing
Pet Food Experts, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-30. The breach occurred from 5/1/2022 to 5/3/2022. 1 Montana residents were affected.
Affected (this filing): 1
Pet Food Experts, LLC reported a data breach affecting 2 Maine residents. The breach, which occurred between May 1, 2022, and May 3, 2022, was discovered on June 3, 2022. The incident was described as an external system breach (hacking), where threat actors acquired names or other personal identifiers in combination with Social Security Numbers. Affected individuals were notified on June 30, 2022, and offered 12 months of identity theft protection services through Experian.
Affected (this filing): 2
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.