Author Topic: A false positive from avast  (Read 3104 times)

0 Members and 2 Guests are viewing this topic.

Offline AliA88

  • Jr. Member
  • **
  • Posts: 20
A false positive from avast
« on: March 23, 2021, 07:49:31 PM »
A false positive was found by avast, I was watching youtube, and i was on a channel called kitboga he is very well know in the utube community with over 1 million subs, he loves catching scammers and trolls them, he has always made sure people are aware of these scams and tells people how to stay safe. So i went on youtube typed his name in the youtube search bar and then clicked on his channel and it appeared no issue was apprant. Now i was a bit behind on his channel and he had 2 new videos i wanted to catch up on. So while his channel was open in the browser via youtube i right clicked on his channel name to open another tab with another instanace of his channel open so i can view the other video afterwards, but doing this avast throws up the alert i checked the url via virus total and the link is clean: https://www.youtube.com/channel/UCm22FAXZMw1BaWeFszZxUKw

Please see attached pic

Thank you

Offline bob3160

  • Avast Überevangelist
  • Probably Bot
  • *****
  • Posts: 48524
  • 64 Years of Happiness
    • bob3160 Protecting Yourself, Your Computer and, Your Identity
Re: A false positive from avast
« Reply #1 on: March 23, 2021, 08:03:32 PM »

Report a false positive (select file or website)
https://www.avast.com/false-positive-file-form.php

Free Security Seminar: https://bit.ly/bobg2023  -  Important: http://www.organdonor.gov/ -- My Web Site: http://bob3160.strikingly.com/ - Win 11 Pro v22H2 64bit, 16 Gig Ram, 1TB SSD, Avast Free 23.5.6066, How to Successfully Install Avast http://goo.gl/VLXdeRepair & Clean Install https://goo.gl/t7aJGq -- My Online Activity https://bit.ly/BobGInternet

Offline AliA88

  • Jr. Member
  • **
  • Posts: 20
Re: A false positive from avast
« Reply #2 on: March 23, 2021, 08:10:35 PM »
Done, I have also checked the link for any re directing its perfectly clean, no idea why avast is throwing this error