Carlos Ramos

Thanks for the advice, will switch to the release files and create the git repo myself, ¿any Idea about the questions?

So for the new installation, I cloned the code from github and switch to tag v4.0.0 (hopefully this way I know if a file have changed). Copied the config file and the plugins directory from my previous installation and uninstalled the VideoAds plugin from the web app, only the default plugins remain. Also had to do a `composer install`. All this in order to keep the database intact and not have to configure the entire adserver again. Just two questions remain: Since the plugins directory is not directly under source control. How can I make sure none of the default plugins are compromised?. Does Revive store any code in the database, is there a chance that the problematic code is in the database and not in the files? Thanks for your time.

Hi Erik, Thanks for your reply. The adserver is installed at the root of the site, no sub-folder. Something like adserver.example.com. And yes this is google webmaster tools. The problem has escalated and now the hosting provider is saying the same about the phishing. I'll proceed with the cleanup today and see what happens. Here is the screenshot you asked:

Hi there, I setup a Revive Adserver about a month ago and right now is marked as a phishing site by Google and others. The installation is stock the the exception of a plugin for video ads. I plan to install from scratch again and not use this plugin anymore. But I wanted to ask if there is any know issue that could provoke this problem. Google is marking this paths as deceptive pages: /www/admin/ /www/admin/dashboard.php /www/admin/index.php /www/admin/stats.php Any advice you may have is welcome. Thanks. The video plugin we use is http://www.reviveadserverplugin.com/product/html5-video-audio-ads-plugin/