Print EZ, Inc
ent_31fa0fdeb97f22103988d9c6
Disclosures
4
State AG · 4 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
1
as filed · State AG MA
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Print EZ, Inc
- Normalized
- print ez— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- printez.com
Disclosure history (4)newest first
- New Hampshire State AGas victim2019-02-19
Print EZ, Inc. notified the NH AG of a breach affecting payment card data (name, card number, CVV) for customers who shopped between Sept 2016 and Sept 2018. A suspicious file was inserted into the e-commerce site. Print EZ modified its checkout process and notified customers via media and website posting. No specific count of affected individuals was provided.
- Montana State AGas victim2019-02-15
Print EZ, Inc. notified customers of a cybersecurity incident affecting its e-commerce website, printez.com. A suspicious file was inserted into the site between September 1, 2016, and September 23, 2018. The incident potentially exposed customer names, credit card numbers, expiration dates, and CVVs. Print EZ discovered the anomaly on December 14, 2018, removed the file, and modified its checkout process. No specific count of affected individuals was provided.
- Massachusetts State AGas victim2019-02-15
Print EZ Inc reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2019-02-15. 1 Massachusetts residents were affected. The report records the breach type as electronic.
- California State AGas victim2019-02-15
Print EZ, Inc. disclosed a data breach affecting customer payment card information (name, address, card number, expiration date, CVV) collected via its e-commerce website between September 1, 2016, and September 23, 2018. The company identified a suspicious file inserted into its website during a routine review. While the exact impact of the file was undetermined, the company notified customers via media and website postings in February 2019. The incident is classified as hacking with unknown specific variety.