Got a notification for a data leak on the Dark Web, but no way to verify the actual password that is involved.
Detailed description:
I use different passwords for accounts on the Web, but the same email address. For at least one account, I have now received a notification that a data leak has occurredon the Dark Web, naming my email address, but showing no information on the password used.
ChatBot next to the notification suggests clicking on the link to “start the email verification process” but there is no link in the email, the webpage showing info in the breach, so how to get there?
PS
BTW Norton, if you are listening in, it is a complete disaster to reach your support team by chat, as the steps to get there involve clicking through several pages and then getting a verification code, where the button to generate the code just doesn’t work (on 3 browsers).
btw ~ I’ve not needed a verification code for Social Support or Chat Support.
I receive a “verification code” sent to my Norton email address…just by opting Chat now.
On occasion Norton Chat agent wrote: I’m sending you a verification…enter the code back to me. I receive the email and type the number back.
Norton Chat agent usually just asks for my Norton email address.
Note: I am allowing Norton pages content.
Did you review your Norton email address Inbox?
for example:
Maybe, data leak was your email address…not password…meaning, your email address was found on the Dark Web. Did the notice report “password” found on the Dark Web?
thanks for your fast reply - I am in the Norton console, the level of exposure is email, PW, Country, Company, IP Address - so password is included. Neither in the email nor in the console is there any "verification " link, and the chat doesn’t go anywhere (tells me to check for that link).
Apparently the system doesn’t let me upload screenshots here, so text must suffice.
I will check whether there are any restrictions allowing Norton content in the browser like you suggest further above, but neither Edge, Chrome nor Safari reported any blocking.
The solutions article you mention runs into a 404, but it may be the generalist one “what to do when” that can be found elsewhere, which I basically know.
