Heirloom Roses
ent_d57fc71449a37e932e77c5d2
Disclosures
4
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
52,206
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Heirloom Roses
- Normalized
- heirloom roses— 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 (4)newest first
- 🦫Oregon State AGas victim2021-12-17
Heirloom Roses reported a data breach to the Oregon Attorney General. The breach was reported on 2021-12-17. The breach occurred during 2/24/2021 - 10/26/2021. The breach was discovered on 11/17/2021. 52,206 individuals were affected. Notice was sent on 12/17/2021.
- 🐻California State AGas victim2021-12-17
Heirloom Roses notified California AG of a data breach where malicious code was added to its website to capture credit card data. The incident occurred between February 24, 2021, and October 26, 2021. Affected data included names and credit card information. The company engaged forensic specialists, secured the site, and offered 12 months of identity monitoring.
- 🦬Montana State AGas victim2021-12-17
Heirloom Roses reported a data breach to the Montana Attorney General. The breach was reported on 2021-12-17. The breach occurred from 2/1/2021 to 10/26/2021. 210 Montana residents were affected.
- 🌲Washington State AGas victim2021-12-17
Heirloom Roses, a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2021-08-12 and filed notice on 2021-12-17. 3,118 Washington residents were affected. 127 days elapsed between awareness and notification. 181 days to identify the breach. 75 days to contain the breach.