Minnetonka Moccasin Company,Inc.
ent_019e22627a7339bbe5f2e3f761da818b
Disclosures
4
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
38,433
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Minnetonka Moccasin Company,Inc.
- Normalized
- minnetonka moccasin— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 5493005I0XE5FKXIFH05
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- 🦫Oregon State AGas victim2021-04-06
Minnetonka Moccasin Company, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2021-04-06. The breach occurred during 11/25/2020 - 12/25/2020. The breach was discovered on 12/29/2020. 38,433 individuals were affected. Notice was sent on 4/6/2021.
- 🦞Maine State AGas victim2021-04-06
Minnetonka Moccasin Company, Inc. experienced an external system breach where an unauthorized party gained access to its network. The breach resulted in the compromise of names and financial account/payment card information for 153 Maine residents. The incident occurred on November 25, 2020, and was discovered on December 29, 2020.
- 🐻California State AGas victim2021-04-06
Minnetonka Moccasin Company, Inc. notified the California Attorney General of a data security incident involving its website. Payment card information (account number, expiration date, CVV) and names of customers who made purchases between November 25, 2020, and December 25, 2020, may have been exposed. The company engaged a digital forensics firm, contained the exposure, and reported the incident to the FBI.
- 🌲Washington State AGas victim2021-04-06
Minnetonka Moccasin Company, Inc., a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2020-12-29 and filed notice on 2021-04-06. 821 Washington residents were affected. 98 days elapsed between awareness and notification. 34 days to identify the breach. 0 days to contain the breach.