VGVanguard Group
Disclosed Apr 5, 2017·9y9 years ago·1 affected·Confirmed
What is known
| People affected | 1 (as reported by the organization) |
|---|
| Disclosed | Apr 5, 2017 |
|---|
| Happened | Jun 7, 2017 |
|---|
| Attack | Not stated |
|---|
| Data exposed | Not stated |
|---|
| Sector | Other · US |
|---|
| Status | Confirmed |
|---|
Other breaches at Vanguard Group
| Breach | Disclosed | Attack | Sector | Status | Affected |
|---|
| Disclosed Mar 6, 2018Mar 6, 20188y8 years ago | Mar 6, 20188y8 years ago | Not stated | Other | Confirmed | 1 |
| Disclosed Dec 23, 2015Dec 23, 201510y10 years ago | Dec 23, 201510y10 years ago | Not stated | Other | Confirmed | 1 |
| Disclosed Feb 24, 2014Feb 24, 201412y12 years ago | Feb 24, 201412y12 years ago | Not stated | Other | Confirmed | 59 |
| Disclosed Apr 10, 2013Apr 10, 201313y13 years ago | Apr 10, 201313y13 years ago | Not stated | Other | Confirmed | Unknown |
History of this record
- 2026-09-25 · disclosed: 2017-07-10 to 2017-04-05 · backfill source
- 2026-09-25 · added · backfill source
First seen 2026-09-25 (Indiana AG), confirmed by Indiana AG. Record counts are as reported. Not legal advice.
Everything about Vanguard Group
