Huggins Insurance Se
ent_96feb5af083ef135f86886a3
Disclosures
4
HHS OCR · State AG · 3 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
5,725
nationwide · HHS OCR OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Huggins Insurance Se
- Normalized
- huggins insurance— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- hugginsseniorbenefits.com
Disclosure history (4)newest first
- OREGONHHS OCRas victim2019-05-24
Huggins Insurance Services, Inc. reported to HHS on 2019-05-24 a Hacking/IT Incident affecting 5,725 individuals. Breached information located on Email. Employees were victims of an email phishing scheme affecting ePHI including names, addresses, DOB, driver's license, SSN, claims, financial, and clinical data. The BA implemented safeguards and retrained staff.
- New Hampshire State AGas victim2019-05-24
Huggins Insurance, an Oregon-based insurance broker, notified the New Hampshire Attorney General of a data security incident involving two NH residents. On January 16, 2019, Huggins discovered unauthorized access to employee email accounts via phishing. The breach exposed names, SSNs, driver's license numbers, health insurance policy numbers, credit/debit card numbers, financial account numbers, and medical information. Huggins engaged forensic investigators, notified the FBI and credit bureaus, and offered one year of complimentary credit monitoring to affected individuals.
- Montana State AGas victim2019-05-24
Huggins Insurance notified Montana residents of a data breach where unauthorized individuals accessed employee email accounts starting January 16, 2019. The incident exposed names, SSNs, driver's licenses, financial account numbers, and medical information. Huggins engaged forensic investigators and offered one year of credit monitoring.
- Oregon State AGas victim2019-05-24
Huggins Insurance reported a data breach to the Oregon Attorney General. The breach was reported on 2019-05-24. The breach occurred during 11/25/2018 - 1/24/2019. The breach was discovered on 4/3/2019. 5,725 individuals were affected. Notice was sent on 5/24/2019.