Hanna Andersson LLC
ent_2f4cf0b96a78a73e600e0c81
Disclosures
5
State AG · 5 jurisdictions
Incidents
2
filings grouped by incident
Max affected reported
8,816
as filed · State AG WA
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Hanna Andersson LLC
- Normalized
- hanna andersson— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- hannaandersson.com
Disclosure history (5)newest first
- 🦬Montana State AGas victim2020-01-15
Hanna Andersson LLC reported a data breach to the Montana Attorney General. The breach was reported on 2020-01-15. The breach occurred from 9/16/2019 to 11/11/2019. 559 Montana residents were affected.
- 🌴South Carolina State AGas victim2020-01-15
Hanna Andersson, LLC notified customers of unauthorized access to website purchase data between Sept 16 and Nov 11, 2019. Affected data included names, addresses, and full payment card details (number, CVV, expiration). The company secured the platform, engaged forensic experts, and offered 12 months of identity theft protection.
- 🐻California State AGas victim2020-01-15
Hanna Andersson, LLC reported a security incident involving unauthorized access to its e-commerce website between September 16 and November 11, 2019. An unauthorized third party accessed customer data including names, addresses, payment card numbers, CVV codes, and expiration dates. The company re-secured its platform, engaged forensic experts, and offered credit monitoring services to affected customers.
- 🦫Oregon State AGas victim2020-01-15
Hanna Andersson, LLC reported a data breach to the Oregon Attorney General. The breach was reported on 2020-01-15. The breach occurred during 9/16/2019 - 11/11/2019. The breach was discovered on 12/5/2019. Notice was sent on 1/15/2020.
- 🌲Washington State AGas victim2020-01-15
Hanna Andersson, LLC, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2019-12-05 and filed notice on 2020-01-15. 8,816 Washington residents were affected. 41 days elapsed between awareness and notification. 80 days to identify the breach. 0 days to contain the breach.