1. Michael Ginsburg

    FYI, got this when trying to access the link:

    Google Chrome has blocked access to this page on wp-abtesting.com.
    Content from demos.shapingrain.com, a known malware distributor, has been inserted into this web page. Visiting this page now is very likely to infect your computer with malware.


  2. chris mccoy

    max ab from max foundry is a good one also


  3. Jeffro

    @Michael Ginsburg – That is weird. The page loads fine in both FireFox and Google Chrome for me without any warnings.


  4. Michael Ginsburg

    @chris mccoy

    This one hasn’t been updated in almost 2 years and showing compatibility only up to WP ver 3.2.1.

    This would probably put it in the ‘dead plugin’ category (i.e support has ENDED) and I would therefore not feel comfortable using it on my site.

    Any other suggestions?


  5. Ed Sutherland

    I receive the same malware warning from Chrome 27.0.1453.116.


  6. Jeffro

    Ok, I too finally received the malware message in Google Chrome. That’s a shame because the AB Testing site is not bad. I’ve put the domain through a couple of scanners and they all report the site is clean.


    I suppose the domain has a bad history previous to the two months they have owned the domain. Any of you folks know how they could remove that message?


  7. Jonathan Dingman

    @Michael Ginsburg – I got the same warning. Wonder what’s going on there.


  8. Jeffro

    Ok, well, in doing some research, I suggest the folks behind WP-ABTesting.com go through the steps provided here https://support.google.com/webmasters/answer/2600725 and at the end, request Google review their domain as it is now. I bet it’s clean now but the Malware warning is cached or something.


  9. Jordi Cabot

    Really weird (and really unfortunate that this is happening right now :-( ).

    Google webmaster tools says that the site is clean. We´ll investigate why some of you are getting the message.

    Thanks for your patience!


  10. Jeffro

    @Jordi Cabot – Yep this sort of thing sucks but thankfully, you are in Beta :) Hope Google can quickly get this mess cleaned up.


  11. Jordi Cabot

    @Michael Ginsburg
    Hi Michael, really sorry about this. We have finally found out why Google flagged us as malware. Full details here: http://wp-abtesting.com/worst-timing-google-flagged-our-site-as-malware-on-our-prelaunch-announcement/
    (in case you still see the malware message, the short story is that yesterday Google blacklisted by mistake the theme shop where we bought our theme and flag as malware all sites that had a link somewhere to that web)
    So, worst timing ever but I hope you still decide to evaluate our service, you can join the beta in our site or just send us an email to info@wp-abtesting.com and we’ll set you up


  12. Jordi Cabot

    @Ed Sutherland -Hi Ed, sorry about this. We have explained in a previous comment this bizarre situation. Let us know ( info@wp-abtesting.com if you still see the malware message) if you´d like to join the beta and we´ll set you up


  13. Jordi Cabot

    @Jonathan Dingman -Hi Jonathan, please see our replies above. Hopefully, we can get now a fresh start with all of you! Let us know if you´re interested in joining the beta and we´ll set you up!


  14. Ted Clayton

    @Jordi Cabot explains the snafu:

    … Google flagged us as malware. Full details here: http://wp-abtesting.com/worst-timing-google-flagged-our-site-as-malware-on-our-prelaunch-announcement/
    (in case you still see the malware message, the short story is that yesterday Google blacklisted by mistake the theme shop where we bought our theme and flag as malware all sites that had a link somewhere to that web) – [emph. added]

    My condolences to Mr. Cabot and the WP-ABTesting project … and to our host Jeffro and his WPTavern website. The unintended story that this has become, does appear to be mostly/largely/probably just ‘unfortunate’ … but with some meaningful caveats.

    I read the “Full details” post on WP-ABTesting, and they do deserve credit for responding/reacting to the Google identification of a security issue. The response does fall short in 2 areas, though.

    Secondly, it implies that Google is, ‘[Sigh], you know, such a mindless clod, negligently wreaking other kids projects’. That’s a tad rich. Google run tech/security-circles around everybody here.

    Firstly, what actually is going on at/with Theme Forest, “the theme shop where we bought our theme“? And, the “Full details” post offers a link explicitly to this, quote “WordPress theme we bought“, end quote, which is in fact not a link to the theme they acquired, but simply dumps us at the Theme Forest front door …. where we see it loudly proclaimed that they sell, quote, “10,785 Site Templates and Themes from $3”, end quote.

    It is obviously of interest, which specific theme (out of ten thousand offerings) was actually involved … whether some think that was important, or not. That information would be a key part of the “Full details” … and has been made, really, ‘conspicuous by its absence’.

    Is there something icky/dubious going on at Theme Forest? This is a well-known provider of themes & etc, for the wider WordPress community. Are those folks actually a slippery or fast-and-loose outfit (or too accompanying of such), and we should be saying so? Are Google really security-lamers, or is that a red herring to deflect attention from ‘back-alley’ behavior within the WordPress commercial sector?

    I get no impression that WP-ABTesting were active ‘bad actors’ here, in terms of the reported security-issue … but they do seem to be giving this affair that ol’-time ‘Move along now – nothing to see here’, treatment.

    … (don’t be scared, we will hide all the math from you, just keep reading!) …

    Unfortunately, my site is on my localhost, and I can’t test WP-ABTesting. If I was online, though, I would at least be checking out the terms of their offer closely. (I won’t ‘sign on’, under every & any set of terms that we see offered/required, even for things that are of interest – and WP-ABTesting is of interest.)

    But as far as hiding the math (and other tech-details) … please, yes, do abuse me! ;)


  15. Tom Gasville

    @Ted Clayton – I don’t see any caveats here. They wanted to promote their new service, yes, but considering being blacklisted as a marketing strategy is too much for me. I’ve also launched online beta/demo programs and the last think you want is your web site down.

    About Google, the methodology of ‘shoot first, then ask’ that is used when putting a website in a blacklist is, in my opinion, too severe. I’m sure they have the tools and technology to check false positives more accurately, specially when, as it seems in this case, the site wp-abtesting.com was safe according to Google Webmaster Tools.

    About Theme Forest, Michael Ginsburg in a previous comment also mentioned that the problem he found was with ShapingRain, which is a theme provider that sells in Theme Forest. As far as I know, they only sell the Just Landed theme for WordPress. Following the comments (and also the content) in WP-AB Testing explanatory blog post you can also see that explicitly mentioned. It wasn’t hard to find for me.

    I don’t see the point about second interpretations of what here happened. Maybe I’m too naive but, you know, I was never a follower of conspiracy theories. To me, Neil Armstrong walked on the moon, and Mr. Cabot’s web just went blacklisted by mistake in a promotion day. It seems to be solved now. End of story.


  16. Jeffro

    Just in case people wanted to follow along, the commentary on HackerNews about Google blacklisting sites in general is pretty good https://news.ycombinator.com/item?id=6242533 I’d hate to be the victim of such an event, especially if it damaged my companies reputation and lost me a ton of money. Why Google Webmaster tools doesn’t alert website administrators of the malware warning is beyond me.


  17. Ted Clayton

    @Tom Gasville

    … it seems in this case, the site wp-abtesting.com was safe …

    From what we can tell/see, the WP-ABTesting site itself was not doing whatever is was that got Google’s attention … but they were linked-in or networked with others, who were & did.

    It’s worth noting, especially for the less-technical and for those who think they need networked services to run a web-business (or to be cool), that being linked-together can make multiple web-entities functionally a single site. When a problem arise with one member of such a network, no matter how inconsequential they might seem, what’s going on with them can affect (ie, eg, ‘take down’) the whole network. Being more independent may seem old-fashioned, but it’s the stronger & smarter security-posture.

    I don’t see the point about second interpretations … It seems to be solved now. End of story.

    On the contrary, Mr. Gasville, we have a Comment section as this, precisely & expressly to invite & explore “second interpretations”.

    Theme Forest, and parent company Envato, have been the topic of controversy within the WordPress community, for some while now.


  18. Ted Clayton


    I did not have real high hopes for this page, but stand pleasantly corrected. ;)

    When I looked, the top comment showing (also on Jeffro’s link), begins:

    I’ve suffered from the same malware issue earlier. Since we use ad networks for advertising it works as follows. 1 ad network has about 3000 different ads running in different locations. If any of those domains get compromised and blacklisted and Google notices that you served something from that domain – BOOM![emph. added]

    This reinforces the remark I made to Tom Gasville, that having yourself ‘all networked up’ with gawd-knows who-all & what-all, means that when any one of your network partners does something squirrelly, shady, too-rule-bendy or downright nefarious … the whole dang bunch of you are taking the fall!.

    It’s not just “ads”. It’s not just “image-linking”. ANYTHING too far outa the envelop, on any of potentially huge numbers of sites, involving linkages that may be totally unknown to many of them, can become a problem for all of them.

    This is what appears to have happened to WP-ABTesting.


Comments are closed.

%d bloggers like this: