Jump to content

www.yola.com blocked


Recommended Posts

Hi

It has come to my attention from some of our customers who use Malwarebytes that www.yola.com (208.75.208.173) has been blocked from your program. I would like to find out why we have been blocked and how we can be unblocked.

We at yola.com do not tolerate malware of any kind and although we provide a sitebuilder and hosting facility we actively will shut down sites that contrevene our terms and conditions as soon as we find them

Thanks in advance

Jason

Link to post
Share on other sites

It was blocked due to the following. I never received a response from your abuse dept concerning this;

20090930151806	208.75.209.79	server79.inetservices.com	sitebuilder.yola.com	http://sitebuilder.yola.com/sites/S3/Dd2d/D644/D726/D67e/Ud50347136e664412bbcbe76627446d2d/8a49866b23fe66b50123feac3a6a05a6/resources/shell.txt

20100206032410 208.75.208.172 server172.inetservices.com viruses.yolasite.com http://viruses.yolasite.com/resources/SpySheriff.zip

20100206032412 208.75.208.172 server172.inetservices.com viruses.yolasite.com http://viruses.yolasite.com

I noticed the viruses.yolasite.com site appears to have been shut down, but alas the first one has not, and contains a PHP IRC bot. If you can shut the sitebuilder.yola.com site down and/or clean up the malware hosted there, I'll get the block removed.

Link to post
Share on other sites
  • 3 months later...
It was blocked due to the following. I never received a response from your abuse dept concerning this;

20090930151806	208.75.209.79	server79.inetservices.com	sitebuilder.yola.com	http://sitebuilder.yola.com/sites/S3/Dd2d/D644/D726/D67e/Ud50347136e664412bbcbe76627446d2d/8a49866b23fe66b50123feac3a6a05a6/resources/shell.txt

20100206032410 208.75.208.172 server172.inetservices.com viruses.yolasite.com http://viruses.yolasite.com/resources/SpySheriff.zip

20100206032412 208.75.208.172 server172.inetservices.com viruses.yolasite.com http://viruses.yolasite.com

I noticed the viruses.yolasite.com site appears to have been shut down, but alas the first one has not, and contains a PHP IRC bot. If you can shut the sitebuilder.yola.com site down and/or clean up the malware hosted there, I'll get the block removed.

Link to post
Share on other sites

I am unable to disable sitebuilder.yola.com as that it the main url for the site builder i.e. the tool that over two million users use to build their websites and it is not one single user's site. However you will notice that the malware shell.txt has been removed on the offending site and as such could you now remove the block on yola.com?

Thanks

Link to post
Share on other sites

Disabling one or two is great, but I'd prefer you actually have a working abuse@ address. I'd also prefer you have *something* that checks the files your users upload, for malicious content, and checks your server/network logs for the same (a stretch I know, and a logistics nightmare - but mandatory in todays interwebs).

I'll get the block removed now the last one has been taken care of, but bear in mind, your service is heaven to the bad guys, due to your not checking anything, and not having a working abuse address for people to report malicious content to - so without taking steps to correct this, this kind of issue is set to repeat itself.

Link to post
Share on other sites

I've tried sending to abuse@yola.com and abuse@yolasite.com previously, but they've either bounced back (in the case of the abuse@yolasite.com), or gone unanswered.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.