Website blocked: URL:Blacklist / HTML:Script-inf [Susp]

[kontakt61]

Hi,

my website htXps://schreinerei-ackermann.de/ (Wordpress) is blocked by avast (and avg):

Reason: URL:Blacklist


Screenshot:
https://www.bilder-upload.eu/bild-26b8f7-1600758606.jpg.html


To get access to Wordpress backend I excluded the url in avast settings.

Then I tried to login into backend (htXps://schreinerei-ackermann.de/wp-admin) but this was also blocked:

Reason: HTML:Script-inf [Susp]


Screenshot:
https://www.bilder-upload.eu/bild-89a34c-1600758867.jpg.html


This was checked so far:

Wordpress-Plugin "Wordfence" (Premium) -> no problems detected

GoogleSearchConsole -> no problems

https://transparencyreport.google.com/safe-browsing/search?url=https:%2F%2Fschreinerei-ackermann.de%2F
->  no problems, no malware detected

https://www.virustotal.com/gui/url/c70a916ed18c0538fc31ac1b947311455b0e96b8f925b2cc4a1cc239b797e5b6/detection
-> 5 engines detected this URL (but unfortunately no further information available)

https://sitecheck.sucuri.net/results/https/schreinerei-ackermann.de
-> no malware found / site is not blacklisted

https://urlscan.io/result/3437f9b5-eac6-4177-a6b3-db921e0fc021/
-> no problems

https://observatory.mozilla.org/analyze/www.schreinerei-ackermann.de
-> not quite shure about the results

https://unmask.sucuri.net/security-report/?page=schreinerei-ackermann.de
-> no problems

https://retire.insecurity.today/#!/scan/f2c63d9896442d4c2ea547f381a3cbd3971726a1c5faa94b92e216d144b26808
-> 1 vulnerable library detected / not quite shure about the results



https://www.avast.com/false-positive-file-form.php was used (yesterday).

Wordpress and all plugins are updated.

Could anyone inspect this website, please? Thank you very much for any hints.
How can I get more details about "HTML:Script-inf [Susp]". Where does it comes from inside my website?

Thanks.
Wolfgang

[Milos]

Hello,
detection seems to be fixed now. Test it, please.

Milos

[kontakt61]

Hi,

yes, I just received an email from avg:

Hello,

Thank you for contacting AVG.

Please accept our apologies for the inconvenience caused. The detection by AVG was incorrect and was removed in a recent AVG update...

Everything seems fine - thanks.
Wolfgang