Avast Fixed The Recent False Positive For "api.hive.blog" After Notifying Them

If anyone had issues in the last few days with Avast reporting a false positive on api.hive.blog, you will now find the issue fixed.

If you are using Avast and still get the URL:phishing notification when visiting Hive, update your antivirus.

I had this issue with Avast antivirus giving me an annoying false positive on api.hive.blog for the previous two days, mentioning that connection was rejected as api.hive.blog was infected with URL:Phishing.

Clearly a false positive.

I notified Avast on Sunday, and approximately 10 hours ago, they removed the false positive.

Antivirus software reports false positives with links they include in black lists. I expected they would fix it sooner or later, but the notification persisted for days.

It was annoying enough and also blocked my connection on Peakd, LeoFinance, and Ecency which are the three main ways I use to access the Hive platform, and giving me a hard time.

I had to change manually the default API node on PeakD, but still, the same message appeared as I was (probably) connected to the same node in other apps I couldn't find.

The node belongs to @blocktrades, and while clearly, this is a trusted node, I barely have the technical knowledge to evaluate these situations. Since the problem persisted, I contacted Avast.

I mentioned the issue this Sunday on this official Avast link, where anyone can report a false positive.

Avast also responded to my email, noting they fixed the issue and provided further details in case the problem persisted.

Avast examined the URL and marked the website and links I provided clean.

Antivirus false positives are annoying, but the websites may take a long time to realize an antivirus added a URL in a blacklist.

False positives can create a negative impression on websites, and deter people from using them, limiting the network effect.

We can act when we know there is nothing wrong with a service, and it only takes a couple of minutes to locate the official support link and notify of our findings.

Avast acted professionally, examined my request, and corrected the mistake by removing the false positive.

*Cover on Pixabay

Images, and material in this article are used for research, and educational purposes and fall under the guidelines of fair use. No copyright infringement intended. If you are, or represent, the copyright owner of images used in this article, and have an issue with the use of said material, please notify me.

Find me on:
Medium - Noise Cash - Read Cash - Hive - Vocal - Minds - Steemit - Publish0x - Twitter - Reddit