Paypal-B (Phish) problem with latest version

[REDACTED]

I am experiencing a problem with the Paypal-B (Phish) threat that I have read about and it seemed to have been solved.  Attached are 3 screenshots showing the problem and current avast version.  I updated Avast, restarted computer and the problem still exists.  I would be glad to send in more information if that will help.  I can't seem to find the

[DavidR]

This should already be resolved https://forum.avast.com/index.php?topic=220596.0.

Ensure you have the latest virus definitions update.

[REDACTED]

Thanks for your reply but- I believe  have updated avast and virus database, rebooted (several times).  I had  attached a screenshot with the avast version numbers.  Does that show my version is not up to date?  I ran the avast update and attached the screen showing that it thinks my version is updated.  Am I missing something with the updates that I don't understand?

Still having the problem after rebooting again.

[DavidR]

Try clearing your browser cache, though in theory that shouldn't have an impact.

The link that I gave had a post from one of the avast team, bauerj, who said it should be fixed in the next VPS update and that was some time ago.

[REDACTED]

Thanks again for the reply.  It was not working in both Firefox and Chrome for me.  It is working now in both of them.  I  cleared the cache in Firefox and that (or just restarting firefox) seemed to help.  Very strange that this appeared from nowhere today.

[REDACTED]

OK - false start there.  The warning was coming up on just going to paypal from another vendor.  I clicked on the pay with paypal button and the warning did not happen so I thought it was fixed.  Now the warning came up when I went log into paypal so the problem is still there.

[DavidR]

Yes, it is still there I just tried to log on to my PayPal account and got the alert window, see attached.

Given that this has been acknowledged as a false positive (and had been supposedly fixed) this needs urgent action.

You could use the More Options to add an exclusion, this however, isn't without risk if it is anyway possible it could be a Phish your account details could get harvested.

Edit: See second attachment, indicating my VPS is up to date.

[Asyn]

Hi guys, the latest VPS for me is 181019-10.

[REDACTED]

hmmm -10?  mine is -4 and when I try to update it says the the VPS is up to date.  Maybe I should unistall and reinstall?  The program version says it is up to date also

thanks for your help

[REDACTED]

I've been having this issue all day.  Is there any other choice other than to turn off/uninstall Avast? 

There's no exclusion setting I can see.  Very irritating.

Avast was just updated, restarted, cache cleared, Firefox, windows.

[schmidthouse]

Hi guys, the latest VPS for me is 181019-10.

Yes also.

[DavidR]

Hi guys, the latest VPS for me is 181019-10.

Yes also.

Mine is still reporting 181019-4 as up to date.

Irony of all ironies is ordinarily if there was an out of sync situation like this, VPS version being reported/displayed by the UI is different to what the latest version is. then we/I would suggest an avast repair, but currently that too is screwed up (certainly on this XP Pro system).

Edit: my win10 laptop is also reporting version 181019-4 as up to date. And there is no Repair option on that either.

Edit 2:  Am I going daft or what, I used the Uninstall option (and I can't recall doing that to get to Repair, I used the Change option) and found Repair there.  Did a Repair on both systems and a manual VPS update and both are still reporting VPS version 181019-4 as up to date.

[schmidthouse]

Hi guys, the latest VPS for me is 181019-10.

Yes also.

Mine is still reporting 181019-4 as up to date.

Irony of all ironies is ordinarily if there was an out of sync situation like this, VPS version being reported/displayed by the UI is different to what the latest version is. then we/I would suggest an avast repair, but currently that too is screwed up (certainly on this XP Pro system).

Edit: my win10 laptop is also reporting version 181019-4 as up to date. And there is no Repair option on that either.

Interesting. I believe both Asyn and myself are running betas......I wonder if that would account for different builds.

[DavidR]

Hi guys, the latest VPS for me is 181019-10.

Yes also.

Mine is still reporting 181019-4 as up to date.

Irony of all ironies is ordinarily if there was an out of sync situation like this, VPS version being reported/displayed by the UI is different to what the latest version is. then we/I would suggest an avast repair, but currently that too is screwed up (certainly on this XP Pro system).

Edit: my win10 laptop is also reporting version 181019-4 as up to date. And there is no Repair option on that either.

Interesting. I believe both Asyn and myself are running betas......I wonder if that would account for different builds.

I would have thought that the VPS update would be the same vpsnitro location for beta or regular release.  Whilst the IP address may differ as there are many servers required for updates.

[Asyn]

Hi guys, I forwarded it to threat lab on Slack. Lets see...