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.

[Alfa1]

Does BB block XRumer? Some forums seem to be getting hacked by this.

I didn't check vbSEO sitemap yet, but since almost everyone uses it, this would be important to resolve.

I entered bugs and feature requests into trac: http://trac.assembla.com/vb-bad-behavior/report/1
I see you already have a spammer in the bug tracker.

[Lee G]

Finally got everything up and running smooth again over night and its worth it
My sitemap is back. The guys over at vbseo have been helping with tips on what server resources to increase

Added a few corporate spiders to the block list to free up some resources along with killing a lot of unused garbage.

The corporate spiders are the ones that do nothing else than search your forums for companies. No online public access for any of their results. The likes of Spin3r etc

Im already starting to see genuine results from using this

[Eric]

Originally Posted by Lee G

Finally got everything up and running smooth again over night and its worth it
My sitemap is back. The guys over at vbseo have been helping with tips on what server resources to increase

Added a few corporate spiders to the block list to free up some resources along with killing a lot of unused garbage.

The corporate spiders are the ones that do nothing else than search your forums for companies. No online public access for any of their results. The likes of Spin3r etc

Im already starting to see genuine results from using this

Was it a problem with BB for the sitemap, or did it turn out to be something else?

Originally Posted by Alfa1

Does BB block XRumer? Some forums seem to be getting hacked by this.

I didn't check vbSEO sitemap yet, but since almost everyone uses it, this would be important to resolve.

I entered bugs and feature requests into trac: http://trac.assembla.com/vb-bad-behavior/report/1
I see you already have a spammer in the bug tracker.

For XRumer... honestly, I'm not sure. And thanks for everything you've logged in Trac - I've been able to close some of them as fixed.

[Simon Lloyd]

I added this today, seems greate because i want to get rid of the stuff from my .htaccess, anyway, it may be that i don't understand it properly yet but the few already blocked seem to come from google although im probably wrong:
Code: 69920ee5

GET /forumz/showthread.php?t=206014 HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: no
Connection: Keep-Alive
Cookie: vbet_language=no; tccsessionhash=1cf31725ad89f8567e17c690468d1efa; tcclastvisit=1302894970; tcclastactivity=0; vbet_sessionUsed=1; __utmc=118899148; __utma=118899148.1559634400.1302894986.1302894986. 1302894986.1; __utmb=118899148.1.10.1302894986; __utmz=118899148.1302894986.1.1.utmcsr=google|utmc cn=(organic)|utmcmd=organic|utmctr=convertere%20fr a%20excel%20til%20txt%20fil%20vba; __utmv=118899148.usergroup-1-Unregistered%20%2F%20Not%20Logged%20In
Host: www.thecodecage.com
Referer:
User-Agent: Mozilla/4.0 (compatible; MSIE 999.1; Unknown)
X-Rewrite-Url: /forumz/showthread.php?t=206014

It seems to show and organic view from google being blocked, i am using the API key but not reverse proxy or verbose.

This is their host: 21.79-160-180.customer.lyse.net
and this is their IP: 79.160.180.21

I use vbenterprisetranslator (paid version) if that helps.

Any ideas?

[Lee G]

Thanks for this mod Eric.
It not only saved my forum but also the contents of a sub folder when some nice Russian person decided to attack my server today.

They were hitting me with all forms of their favorite toy.
libwww-perl/5.811
libwww-perl/5.812
libwww-perl/5.803
libwww-perl/5.837

The logging of blocked ip is brilliant for tracking that kind of hit down

Im now over the 16k logged ips in the short time running this

The vbseo sitemap. I just set it to run when Im up, so if it stops, I can complete the daily update. Without the mod running, the sitemap runs fine. If it runs when the low life that inhabit the internet are on a porn break, it runs fine

[Simon Lloyd]

Maybe this thread explains why some organics are being blocked http://answers.microsoft.com/en-us/w...1-4371c27ca816

EDIT: i just googled Mozilla/4.0 (compatible; MSIE 999.1; Unknown)

Test driving the useragent at http://www.botsvsbrowsers.com/Simula...%3B+Unknown%29 shows:
Method: GET
Request Status: 200 : OK
Content-Length: bytes (~k)
Content-Type: text/html; charset=ISO-8859-1
Server: WebServerX

[Eric]

Anyone want to test out 1.0.3 before I release it tomorrow?

http://trac.assembla.com/vb-bad-beha...%2F&format=zip

Current changelog...

- 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)
- Changes: http://trac.assembla.com/vb-bad-beha...%40trunk%2Fvb3

[Alfa1]

Regarding the Release Candidate: When viewing the log (after pruning) I get this error:
Fatal error: Call to undefined function bb2_log_userid() in /private_html/forum/admincp/vb_badbehavior.php on line 196
Uploading vb_badbehavior.php version 1.0.2 resolves this error.

Fix #3 does not work. Im still getting that issue.

I cant test this for long, because I need issue #2 & #4 fixed. #4 is causing many false negatives.

An interesting note: my big board just had a DDoS attack and server load went trough the roof (Somewhere over 45!!!). Turning on Bad Behavior quickly resolved the situation.

[Eric]

I know why #1 is happening - #3 may need some time to work itself out, since it's based on cookies as well. Not much I can do about #4 - #2 you may just need to whitelist the php script - you can enter the URL into ./includes/whitelist.ini

[Eric]

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)
• Changes: http://trac.assembla.com/vb-bad-beha...%40trunk%2Fvb3