West Music
ent_8b5aad4189e0e56232e4217d
Disclosures
5
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
56,335
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- West Music
- Normalized
- west music— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (5)newest first
- 🦬Montana State AGas victim2017-10-13
West Music reported a data breach to the Montana Attorney General. The breach was reported on 2017-10-13. The breach occurred from 7/21/2017 to 8/9/2017. 2 Montana residents were affected.
- 🌲Washington State AGas victim2017-03-06
West Music Company, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2017-02-06 and filed notice on 2017-03-06. 1,495 Washington residents were affected. 28 days elapsed between awareness and notification. 346 days to identify the breach. 0 days to contain the breach.
- 🦬Montana State AGas victim2017-03-03
West Music Company reported a data breach to the Montana Attorney General. The breach was reported on 2017-03-03. The breach occurred from 2/1/2016 to 12/31/2016. 267 Montana residents were affected.
- 🐻California State AGas victim2017-03-03
West Music Company notified California regulators of a data breach involving its third-party payment processor, Aptos. Unauthorized access occurred between February 2016 and December 2016, affecting payment card information (card numbers, expiration dates, names, addresses, emails) for transactions made on westmusic.com and percussionsource.com. The incident was discovered on February 6, 2017, after law enforcement requested a deferral of disclosure. West Music established a call center for affected customers.
- 🦫Oregon State AGas victim2017-03-03
West Music Company reported a data breach to the Oregon Attorney General. The breach was reported on 2017-03-03. The breach occurred during 2/1/2016 - 12/31/2016. The breach was discovered on 2/6/2017. 56,335 individuals were affected. Notice was sent on 3/3/2017.