Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Capital One/Amazon Cloud Data Breach of 2019 does not appear in monitor.firefox.com

  • 1 réponse
  • 1 a ce problème
  • 8 vues
  • Dernière réponse par RiverboatSam

RiverboatSam
RiverboatSam
more options

I've received notice via a class action suit settlement that my e-mail address was acquired in a data breach of Capital One / Amazon Cloud Services in March-July of 2019. I cannot find this on monitor.firefox.com - nor does Capital One appear in the comprehensive monitor list of all data breaches. Is there a way to alert firefox of this breach and/or why is this breach not appearing there? Thanks.

I've received notice via a class action suit settlement that my e-mail address was acquired in a data breach of Capital One / Amazon Cloud Services in March-July of 2019. I cannot find this on monitor.firefox.com - nor does Capital One appear in the comprehensive monitor list of all data breaches. Is there a way to alert firefox of this breach and/or why is this breach not appearing there? Thanks.

Toutes les réponses (1)

RiverboatSam
RiverboatSam Auteur de la question
more options

Oh, yeah - I got mail from the settlement folks indicating my info was stolen. There's even a CNN web article about it that I missed seeing from over 2 years ago: https://www.cnn.com/2019/07/29/business/capital-one-data-breach/index.html I guess Firefox Monitor missed it too. Maybe it has something to do with the way Firefox gets notified (or not) as well (?).