Integration with vBulletin - vB Bad Behavior

/**
* vB Bad Behavior is free software; you can redistribute it and/or modify it under
* the terms of the GNU Lesser General Public License as published by the Free
* Software Foundation; either version 3 of the License, or (at your option) any
* later version.
*
* This program is distributed in the hope that it will be useful, but WITHOUT ANY
* WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
* PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
*/

What is vB Bad Behavior?
This is an integration of the Bad Behavior software with vBulletin.

What is Bad Behavior?
Bad Behavior is a PHP-based solution for blocking link spam and the robots which deliver it. Bad Behavior complements other link spam solutions by acting as a gatekeeper, preventing spammers from ever delivering their junk, and in many cases, from ever reading your site in the first place. This keeps your site's load down, makes your site logs cleaner, and can help prevent denial of service conditions caused by spammers.

Visit http://bad-behavior.ioerror.us/ for more.

Features
For more information on the features of Bad Behavior (and subsequently this mod) please go to Bad Behavior's site:

http://bad-behavior.ioerror.us/documentation/benefits/

For features related to the mod itself, please take a look at the screenshots.

This mod should work with the entire 3.x series (well, beginning with 3.5), but it's only been tested on 3.8.x. I'm not sure if this works on vB 4.x yet, as I've not tested it - but if you try it out, let me know!

Installation
1. Extract the contents of the zip file.
2. Upload the contents of the `upload` folder to your forum root.
3. Enter your AdminCP and go to Plugins & Products > Manage Products > [Add/Import Product]
4. Import the product using the `product-vb_badbehavior.xml` file.
5. Configure the mod in AdminCP -> vBulletin Options -> vBulletin Options -> vB Bad Behavior Options

Upgrading

vB Bad Behavior
In many cases, all you'll need to do to upgrade is follow the installation instructions above.

The only difference, will be you'll need to allow the files to overwrite. Also, when re-importing the product file, you'll need to set "Allow Overwrite" to "Yes".

Bad Behavior
Bad Behavior's files are at `/includes/bad-behavior/`. If you wish to update manually go to:

http://bad-behavior.ioerror.us/download/

And download the latest development version. Extract the zip, and upload the contents of `bad-behavior` to `/includes/bad-behavior/` allowing the files to overwrite.

Versions
The current version of Bad Behavior this mod is using is: v2.2.14
The current version of Bad Behavior (development) is: v2.2.14

Changelog
Version 1.0.13, 04/23/2013

• Bad Behavior upgraded to 2.2.14

Version 1.0.12, 12/21/2012 -- Released: 02/05/2013

• Bad Behavior upgraded to 2.2.13
• Added some more ranges to whitelist.ini

Version 1.0.10, 09/09/2012

• Bad Behavior upgraded to 2.2.10

Version 1.0.9, 06/17/2012

• Bad Behavior upgraded to 2.2.7

Version 1.0.8, 06/12/2012

• Bad Behavior upgraded to 2.2.6
• New Setting: EU Cookie

Version 1.0.7, 05/04/2012

• Bad Behavior upgraded to 2.2.3
• Cron/Scheduled Task for automatic log pruning added.

Version 1.0.6, 01/04/2012

• Bad Behavior upgraded to 2.1.15

Version 1.0.5, 05/26/2011

• Added option for bypassing users/members.
• If the visitor is a user, and is in usergroup 5, 6, or 7 (admin/mod/super mod) - Bad Behavior is bypassed.
• Modified bad-behavior core to check for Google Web Preview
  • file edited: /includes/bad-behavior/core.inc.php
• Added a link beside the IP address in the log for WhoIs.

Version 1.0.4, 04/28/2011

• Bad Behavior upgraded to 2.1.13 (fixes search engine block issues)
• Added Paypal/Paypal IPN IP address to the whitelist.
• Added payment gateway file names to the whitelist.

Version 1.0.3, 04/21/2011

• Fix #1: Pruning log doesn't work.
• Fix #3: POST more than two days after GET (added support for BB's javascript)
• Fix #5: Cannot modify header information error (suppressed error in BB's function)
• Implemented #6: Filter per key (new admincp option to list keys not to be shown in log)
• Implemented #9: Show link to member profile (if userid is found in headers, link to profile)

Version 1.0.2, 04/10/2011

• Updated /includes/functions_vb_badbehavior.php to:
  • disable Reverse Proxy if Reverse Proxy Addresses are empty
  • distinguish SQL queries using "SET", for example: SET @@session.wait_timeout = 90 - which is used by BB
  • set "offsite_forms" to false by default, as it's not really needed in vB IMHO, and it can cause problems with certain setups
  • cleaned up the bb2_read_settings() function and fixed a typo in one of the vbulletin options calls
• Updated /includes/whitelist.ini to include the following GOOGLE ranges:
  • 74.125.0.0/16
  • 216.239.32.0/19
  • 209.85.128.0/17
  • 66.102.0.0/20
• Updated /admincp/vb_badbehavior.php
  • Log pruning was pruning all logs, despite what was entered for number of days

Version 1.0.1, 04/06/2011

• Bad Behavior upgraded to 2.1.12
• Changed files:
  • /includes/bad-behavior/core.inc.php
  • /includes/bad-behavior/searchengine.inc.php
• "Verbose" admin option now set to "No" by default.

Version 1.0.0, 04/05/2011

• Initial release.

Screenshots
Screenshots can now be seen at: http://www.secondversion.com/images/vb/vb_badbehavior/

I was running out of room for attachments here on vB.org


Development

https://github.com/ericsizemore/vb_b...ree/master/vb3


Only those who "Mark As Installed" will receive support for this modification.

[Teemberland]

I was gonna install this, but I found out it doesn't work with Tapatalk. Update would be nice. Thank you.

[Alfa1]

Originally Posted by viper357

These first two are accessing the forum via Tapatalk, the "mobiquo" is the Tapatalk directory/mod.

To resolve this talpatalk issue, you will likely just have to whitelist the url
/mobiquo/mobiquo.php

At the bottom of the file /includes/whitelist.ini add:
url[] = "/mobiquo/mobiquo.php"

That's it.

[carsafety]

Anyone know a similar whitelist for ForumRunner?

Also, has anyone who installed BadBehavior noticed a significant drop in Google Adsense, Amazon or revenue from other affiliates?

[Simon Lloyd]

I have installed it and it's had no impact on my revenue at all

[ClemsonJeeper]

Please add a whitelist for Forum Runner as well.

All requests come through

<base_forum_url>/forumrunner/request.php
<base_forum_url>/forumrunner/ad.php
<base_forum_url>/forumrunner/image.php
<base_forum_url>/forumrunner/detect.js

Thanks!

[Lee G]

Originally Posted by carsafety

Also, has anyone who installed BadBehavior noticed a significant drop in Google Adsense, Amazon or revenue from other affiliates?

What you should see is an increase in revenue
If you are lucky and it blocks a lot of bad or unwanted hits.
The less hits that people see your your adds on, should increase the views to clicks ratio and increase your earnings marginally

I block a lot more hits by adding extra user agents to one file with a reasonable amount of success

What would be a nice feature would be an option to block ips if they hit x amount of times with a banned user agent. 7 day, 14 day 30day options etc

The normal person will see the page of doom and either go away or look into solving the problem if they want to see the page.
The morons running these spam / scraping scripts will hit constantly
One which hit me this week, hit from at least 50 user agents. Most of which I have banned
I find it a regular thing to see 100 successive hits come in from a banned user agent
Then they come back again later with another user agent when they find that one failed.

[Alfa1]

Originally Posted by ClemsonJeeper

Please add a whitelist for Forum Runner as well.

Is it needed to whitelist it? Is BB blocking anything in Forum Runner?

[viper357]

Originally Posted by Alfa1

To resolve this talpatalk issue, you will likely just have to whitelist the url
/mobiquo/mobiquo.php

At the bottom of the file /includes/whitelist.ini add:
url[] = "/mobiquo/mobiquo.php"

That's it.

Thanks for that, but is there a way to whitelist all BlackBerry IP's? This mod is preventing anybody using a blackberry from accessing the forum. Thanks.

[Alfa1]

It does not block IPs, but user agents. But yeah, you can just whitelist anything blackberry if you want.

I'm not 100% sure about this one. Try:

In whitelist.ini

under

[useragent]
useragent[] = "Mozilla/4.0 (It's me, let me in)"
useragent[] = "Mozilla/4.0 (vBSEO; http://www.vbseo.com)"
useragent[] = "BoardTracker (http://www.boardtracker.com/spider.html) (Mozilla/4.0 compatible; MSIE 6.0; Linux CentOS;)"

ADD:

useragent[] = "Blackberry (Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.0.8) (http://www.blackberry.net/go/mobile/profiles/uaprof/8530_evdo/5.0.0.rdf)"

Eric:
I have 286.000 entries in my logs. Its getting difficult to browse through this. Are entries really deleted from the log after 7 days or did BB block 286.000 attempts in the last week?

It would be very helpful to get an overview of registered members that were blocked. BB enables me to notify my members of troyans and other malware on their PC. So that after the removal of this malware they can freely browse my site. But there is no way that I can find time to review 286.000 entries per week.

Especially the entries that contain vb_login_username:

The IP whois does not work. It links to a white screen. Consider to use another whois service like http://whois.domaintools.com/

[Lee G]

I find the who is bit annoying
It seems to add more nloat and you tend to miss any members that have been inadvertently caught by mistake

Im also finding a lot of ips get through that are listed on Project Honeypot