hello

thank you very much concerned about the safety of our forums

I try running it and I get the following message..

Access denied.

Hi Scott,

Is that the entirety of the message? This may be an issue with the file permissions on the script or with your webserver configuration. Try to set the file permission on the script to 755 and run it again. If that doesn't solve the issue, please send us a PM with a link to the script on your site, and we can take a look.

Thanks
Nick - Chief vB Developer @ SEOvB

Malicous hooks to inject with are
Ajax_complete
init_startup
global_start
A new method which will remain private.

Hope i helped

IMO this seems to have potential. What I think would be the best way to see this workin is the following.

1. Change it from 3 months to 24 hrs. Due to the fact that the report will contain way to many false positives to try and sift through when you run it.

2. Create a table in the DB to store the report info.

3. Create a cron job that runs once a day. When it runs store the info in the previously created table. Maybe also add user id and IP info to the table, may make it easier to identify if it was a valid change to something, or from a hacker.

4. Set up a page in the acp that you can view the daily reports from. Have the ability to prune the entries in the table there by date.

I appreicate this mod very much. I was wondering what if there were malicious things that happened around 6 months ago? should I still use this plugin?

If you're familiar with php then you can just adjust this line:

Change the last "3" to "6" then it'll cover the last 6 months.

Hope that it helps.

I think this scripts output is generally misleading and causes panic where not necessary.

Either you should seriously refine your script and add A LOT more conditions to reduce false positives (and as it seems right now, 95% seems to be only false positives) or discontinue the mod.

Determining if a forum was hacked should be left to specialists. If you let someone who doesn't have a clue run your script, nothing good will come from it.

Hi Disasterpiece,

We understand where you are coming from; the script errs on the side of caution, perhaps too much. This was originally an in-house tool that we used to quickly determine which commonly exploited sets of data needed investigating for forums that had been recently hacked. If time allows, we can refine and update the scan criteria of the script to be more precise.

However, we do disagree that the current script output is misleading and we disagree that it causes unnecessary panic. If a forum owner is concerned that his forum was hacked, which is highly likely given the recent mass attacks on vBulletin forums, we believe that this script is a good starting point for investigation and diagnosis, if the script description and instructions are carefully read and followed.

The script does not stop with a simple 'warning', but provides additional, useful information about what was modified and by whom. More information is better than less, and caution is better than carelessness, so the script provides as much information as it can, for those forum owners with some vBulletin knowledge who can understand the script output, and it also provides the most careful recommendation, for those with less vBulletin knowledge.

We do realize that this script alone is not enough for a diagnosis, which is why we recommend professional help. Speaking of which, we are happy to take a look at your script output via PM, if you have concerns, to clarify your results; we've done this a few times already.

Thanks,
Nick - Chief vB Developer @ SEOvB