Source register · Jul 22, 2026
Capital One Financial media coverage
47 qualifying articles recovered in the first 14 days after disclosure across 7 of seven publisher families.
This site shows how share prices moved after an incident became public. It does not prove that the incident caused the move. Company news, sector moves and the wider market can affect every result. Educational only — not investment advice.
Article-level evidence
What was counted
Every row passed the explicit-company-name, publisher-family and 14-day-window rules. Recorded titles may be normalized from a durable URL or research ledger when the publisher page is blocked or no longer exposes its original metadata.
| # | Publisher family | Window | Date evidence | Framing | Recorded article title | Source |
|---|---|---|---|---|---|---|
| 1 | Bloomberg | First 48 hours | Window verified | Mitigation or action | A tipster's email led to an arrest in the Capital One breach | Publisher page: A tipster's email led to an arrest in the Capital One breach |
| 2 | Bloomberg | First 48 hours | Window verified | Descriptive | Alleged Capital One hacker's work and personal history | Publisher page: Alleged Capital One hacker's work and personal history |
| 3 | Bloomberg | First 48 hours | Window verified | Descriptive | Capital One systems breached, US says | Publisher page: Capital One systems breached, US says |
| 4 | Bloomberg | First 48 hours | Window verified | Adverse event | Capital One touted cloud safety while a hacker was breaching it | Publisher page: Capital One touted cloud safety while a hacker was breaching it |
| 5 | Bloomberg | First 48 hours | Window verified | Mitigation or action | New York opens an investigation of the Capital One breach | Publisher page: New York opens an investigation of the Capital One breach |
| 6 | CNBC | First 48 hours | Window verified | Mitigation or action | Akamai CEO says breaches like Capital One show the need for zero trust | Publisher page: Akamai CEO says breaches like Capital One show the need for zero trust |
| 7 | CNBC | First 48 hours | Window verified | Descriptive | Capital One allegations describe a rare insider-threat case | Publisher page: Capital One allegations describe a rare insider-threat case |
| 8 | CNBC | First 48 hours | Window verified | Adverse event | Capital One breach exposes Social Security numbers and linked accounts | Publisher page: Capital One breach exposes Social Security numbers and linked accounts |
| 9 | CNBC | First 48 hours | Window verified | Mitigation or action | Capital One data breach: five things to do if affected | Publisher page: Capital One data breach: five things to do if affected |
| 10 | CNBC | First 48 hours | Window verified | Adverse event | Capital One shares dive after the breach | Publisher page: Capital One shares dive after the breach |
| 11 | CNBC | First 48 hours | Window verified | Mitigation or action | How to protect yourself from fraud after the Capital One data breach | Publisher page: How to protect yourself from fraud after the Capital One data breach |
| 12 | CNBC | First 48 hours | Window verified | Mitigation or action | How to tell if the Capital One breach affected you | Publisher page: How to tell if the Capital One breach affected you |
| 13 | CNBC | First 48 hours | Window verified | Adverse event | Jamie Dimon's worst fears for banks realized with Capital One hack | Publisher page: Jamie Dimon's worst fears for banks realized with Capital One hack |
| 14 | CNBC | First 48 hours | Window verified | Descriptive | Profile of alleged Capital One hacker Paige Thompson | Publisher page: Profile of alleged Capital One hacker Paige Thompson |
| 15 | CNN | First 48 hours | Window verified | Adverse event | Capital One breach compromises tens of millions of applications | Publisher page: Capital One breach compromises tens of millions of applications |
| 16 | Fox | First 48 hours | Window verified | Mitigation or action | Alleged hacker arrested in Capital One breach | Publisher page: Alleged hacker arrested in Capital One breach |
| 17 | Fox | First 48 hours | Window verified | Adverse event | Capital One breach exposes information of 106 million customers and applicants | Publisher page: Capital One breach exposes information of 106 million customers and applicants |
| 18 | Fox | First 48 hours | Window verified | Adverse event | Capital One customers beware: data exposed | Publisher page: Capital One customers beware: data exposed |
| 19 | Fox | First 48 hours | Window verified | Adverse event | Capital One's breach response misses the mark | Publisher page: Capital One's breach response misses the mark |
| 20 | Fox | First 48 hours | Window verified | Mitigation or action | How to protect yourself after the Capital One breach | Publisher page: How to protect yourself after the Capital One breach |
| 21 | Fox | First 48 hours | Window verified | Adverse event | Noncustomers could still be affected by the Capital One hack | Publisher page: Noncustomers could still be affected by the Capital One hack |
| 22 | Fox | First 48 hours | Window verified | Descriptive | Who is the alleged Capital One hacker? | Publisher page: Who is the alleged Capital One hacker? |
| 23 | Reuters | First 48 hours | Window verified | Mitigation or action | AWS says it was not compromised in the Capital One hack | Archive copy: AWS says it was not compromised in the Capital One hack |
| 24 | Reuters | First 48 hours | Window verified | Adverse event | Capital One breach rattles investors | Archive copy: Capital One breach rattles investors |
| 25 | Reuters | First 48 hours | Window verified | Adverse event | Capital One: hacker gained access to personal information of over 100 million Americans | Archive copy: Capital One: hacker gained access to personal information of over 100 million Americans |
| 26 | Reuters | First 48 hours | Window verified | Mitigation or action | Former Seattle tech worker arrested for Capital One hack | Archive copy: Former Seattle tech worker arrested for Capital One hack |
| 27 | The Wall Street Journal | First 48 hours | Window verified | Adverse event | Capital One breach casts a shadow over cloud security | Publisher page: Capital One breach casts a shadow over cloud security |
| 28 | The Wall Street Journal | First 48 hours | Window verified | Adverse event | Capital One hack hits the bank's reputation | Publisher page: Capital One hack hits the bank's reputation |
| 29 | The Wall Street Journal | First 48 hours | Window verified | Descriptive | Capital One hacking suspect's online behavior | Publisher page: Capital One hacking suspect's online behavior |
| 30 | The Wall Street Journal | First 48 hours | Window verified | Descriptive | Capital One reports data breach | Publisher page: Capital One reports data breach |
| 31 | The Wall Street Journal | First 48 hours | Window verified | Adverse event | Capital One shares fall after the breach | Publisher page: Capital One shares fall after the breach |
| 32 | The Wall Street Journal | First 48 hours | Window verified | Mitigation or action | FBI examining possible data breaches related to Capital One | Publisher page: FBI examining possible data breaches related to Capital One |
| 33 | The Washington Post | First 48 hours | Window verified | Descriptive | Alleged Capital One hacker left a digital trail | Publisher page: Alleged Capital One hacker left a digital trail |
| 34 | The Washington Post | First 48 hours | Window verified | Adverse event | Capital One breach compromises tens of millions of applications | Publisher page: Capital One breach compromises tens of millions of applications |
| 35 | The Washington Post | First 48 hours | Window verified | Adverse event | Capital One's own firewall could not stop a hacker | Publisher page: Capital One's own firewall could not stop a hacker |
| 36 | The Washington Post | First 48 hours | Window verified | Mitigation or action | How Capital One cardholders can protect themselves | Publisher page: How Capital One cardholders can protect themselves |
| 37 | The Washington Post | First 48 hours | Window verified | Mitigation or action | How to stay safe after the Capital One hack | Publisher page: How to stay safe after the Capital One hack |
| 38 | Bloomberg | 48–72 hours | Window verified | Mitigation or action | Amazon contacted customers named by the alleged Capital One hacker | Publisher page: Amazon contacted customers named by the alleged Capital One hacker |
| 39 | Bloomberg | 48–72 hours | Window verified | Mitigation or action | Lawmakers target Amazon and Capital One with an inquiry | Publisher page: Lawmakers target Amazon and Capital One with an inquiry |
| 40 | CNBC | 48–72 hours | Window verified | Mitigation or action | Trump allies open congressional inquiry into Capital One | Publisher page: Trump allies open congressional inquiry into Capital One |
| 41 | Fox | 48–72 hours | Window verified | Adverse event | Capital One and others reported as breach victims | Publisher page: Capital One and others reported as breach victims |
| 42 | Fox | 48–72 hours | Window verified | Adverse event | Capital One breach may be the tip of the iceberg | Publisher page: Capital One breach may be the tip of the iceberg |
| 43 | Fox | 48–72 hours | Window verified | Adverse event | Capital One breach suspect allegedly threatened a company | Publisher page: Capital One breach suspect allegedly threatened a company |
| 44 | The Washington Post | 48–72 hours | Window verified | Adverse event | Capital One hack arrived at a difficult time for Amazon's cloud business | Publisher page: Capital One hack arrived at a difficult time for Amazon's cloud business |
| 45 | Fox | Days 4–7 | Window verified | Descriptive | Capital One data breach: the main takeaway for consumers | Publisher page: Capital One data breach: the main takeaway for consumers |
| 46 | Fox | Days 4–7 | Window verified | Adverse event | Social Security scams could rise following Capital One breach | Publisher page: Social Security scams could rise following Capital One breach |
| 47 | Bloomberg | Days 8–14 | Window verified | Descriptive | Capital One hack poised to boost white-hat crowdsourcing | Publisher page: Capital One hack poised to boost white-hat crowdsourcing |
Framing is local to the headline. Descriptive, adverse-event, mitigation/action and favorable labels do not measure reader sentiment, publisher stance, blame or reputational impact.