Let’s Google Bomb Listbanx/Leadbanx

Okay, I think most of us have been hit by these assholes lately. Thank the gods for MT-Blacklist. However, MT-Blacklist doesn’t stop them from trying to leave comment spam. It hasn’t been a problem for me, but take a look at Scott’s activity log. For two or three days, they’ve been hitting him every 3 or 4 minutes. Frankly, I think that constitutes an attack, and I’m seriously considering contacting the FBI and calling it an attempted denial of service attack.

In the meantime, I think we should Google bomb Listbanx and Leadbanx. At least we can try to drive some traffic away from them, since their goal in comment spamming is to drive traffic to them. Let’s use their own tactics against them.

Kim

7 Responses

  1. Another alternative would be to have an article about them on Slash-dot, that would be enough to drive them into 404-dom. 🙂

  2. I got sick of them too, so I decided to give them a call and found out that it wasn’t them that were doing it. There is a spamer that is hijacking traffic from search engine ranked companies and linking to his sites with their names in his keywords in them by using what ever their slogans or major ranked key words are in his individual sites. There has to be a way for us to figure this out, but so far it has taken me over 5 days to get this far as of Friday.

  3. I’m seeing comment spam attempts from them every three or four seconds for several hours at a time. Grrr! It’s always from the same IP address: 65.81.75.91

    A couple weeks ago, I went to http://www.arin.net, where I typed in the number and found it’s registered to Broadwing, a fairly major telecom carrier (they actually provide services to other telephone companies). I sent a complaint to abuse@broadwing.com. No response. Today, I called them up and after being switched around a bit, got somebody in their Internet division who checked the number and confirmed it was, indeed one of theirs, and that I should re-submit a complaint to both abuse@broadwing.com and emcip@broadwing.com. Let’s see what happens …