Clustered 3 filings across 2 jurisdictions · filed Mar 5, 2021. View entity profile → Other incidents for this victim →
incident inc_537819974d1a4e25 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
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.
Identity (basic) · Government ID · Health (basic)
AR DE
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2021
When the intrusion reportedly occurred, per the linked filings
Feb 16, 2021
Reported by DELAWARE AG filings
Walmart Inc. issued a Delaware state AG breach notification regarding a third-party data hosting service compromise. An unauthorized party accessed records on January 20, 2021, and Walmart was notified on February 16, 2021. Walmart's own systems were not affected. Affected data included names, addresses, DOB, phone numbers, and prescription/medication details. Walmart offered one year of identity monitoring services.
Walmart notified Delaware AG of a breach affecting customer data via a supplier's compromised data hosting service. Unauthorized access occurred Jan 20, 2021; Walmart notified Feb 16, 2021. Data included names, DOB, addresses, and prescription details. Walmart's systems were not directly affected. One year of identity monitoring offered.
Walmart Inc. reported to HHS on 2021-03-05 a Hacking/IT Incident affecting 2,071 individuals. Breached information located on Network Server. The breach involved a business associate compromising PHI (names, addresses, DOB, phone, medication, insurance info).
Affected (this filing): 2,071
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.