Administrative and Maintenance Tools - Multiple Account Detection & Prevention

It happens all of the time. Some members will make multiple accounts to back their own opinion or get an extra vote in a poll. Here's a modification that will detect and prevent multiple accounts, as well as notify the administration about multiple accounts. Inspiration for this modification came from the work of MPDev (creator of the Multiple Account Login Detector) and randominity (creator of the Multiple Account Registration Prevention). This is basically a combination of those two modifications but with new and improved functionality.

This is not an update to the "Multiple Account Login Detector (AE Detector)" nor is it an update to the "Multiple Account Registration Prevention." If you have either one of these (or both of them) installed, you should uninstall them before installing this modification.

With the initial release of Multiple Account Detection & Prevention, I believe that I have fixed previous bugs/complications as well as improved the efficiency and logic of the code. This is my first publicly released modification. I would appreciate any comments and suggestions!

Confirmed! This works perfectly on all vBulletin 3.6, 3.7, and 3.8 versions.

Unfortunately, I cannot give support right now. I may be able to help periodically, but until my schedule yields some more free time, I won't be much support. Please check back in a week or two.

Basic Details
File Edits: None
Template Edits: None
New Files: 6
Hooks/Plugins: 3
Global Phrases: 36
Install Time: 2 Minutes or Less
Install Difficulty: None, Very Easy

Features and Settings
- Login Detection
- Registration Prevention (Multiple Methods)
- Ignore Child Accounts
- Ignored Users
- Ignored Usergroups
- Ignored ISPs
- Prevention Usergroup
- IP Address Based Prevention
- Extended IP Address Prevention
- IP Address Time Inclusion
- Banned Account Check
- Primary Banned Usergroup
- Cookie Expiration Time
- Cookie Refreshing
- Cookie Name
- Cookie Reset
- Multiple Account Reporter
- Reports via PM
- PM Report Recipients
- Reports via New Thread
- Forum for Report Threads
- Verbose Mode
- BB Codes: LIST, URL, CODE

How it Works
With every newly recognized login/registration, an account-counting cookie is set (or added onto) with the member's User ID. Depending on the settings, Multiple Account Detection & Prevention will analyze the cookie during login/registration to see if there are any multiple accounts.

Login Detection offers cookie-checking and reporting. Registration Prevention offers the same thing, plus more advanced features. First of all, when it prevents an account from registering, it actually moves the registrant to the Prevention Usergroup so that the administration can review the case. This also allows for customized privileges for recognized multiple registrants. Registration Prevention also has IP address detection which finds out just as much information about users. Depending on an administrator's preference, this modification can also reban a new registrant if one of their previous accounts has been banned. In fact, if the administration wishes, multiple registrants can simply be denied registration all together.

Whenever there is a detection/prevention, the modification will report the information to the administration through private messages, a new thread, or both (depending on settings). The Multiple Account Reporter can be any valid user.

Known Issues
- vB Optimise users: Reporting via thread seems to get messed up by vB Optimise, so try reporting via PM instead.
- PhotoPost vBGallery users: The registration handling appears to not work properly when PhotoPost vBGallery is enabled.

From what I can tell, these known clashes have been caused by the other modification's coding. The author of vB Optimise will not even work with me to fix it. Until they improve their coding, I'm not sure if I can do anything about these issues. As far as I know, administrators that do not use the above modifications will not have any problems.

Installation / Upgrade
Unzip the package (madp.zip), upload the files to your forum location, and import the product file (allow overwrite if upgrading). Please read the ReadMe.txt file that is packaged with the modification for more information.

Please remember to mark this modification as installed if you use it!
If you like it, nominate it for the Mod of the Month!

Thank you!

[Trek]

Installed, very nice work!

I have a question though. I installed this after realizing I had a problem. How can I go about fixing the problem from current users?

Is there a way to match people by IP so I can see any dupes?

Also, it looks like this mod will check people as dupes whenever they login, is this the case? (If so, it negates my having to worry about issues before I installed this).

Thanks, and again nice work!

[Kiros72]

Originally Posted by Trek

Installed, very nice work!

I have a question though. I installed this after realizing I had a problem. How can I go about fixing the problem from current users?

Is there a way to match people by IP so I can see any dupes?

Also, it looks like this mod will check people as dupes whenever they login, is this the case? (If so, it negates my having to worry about issues before I installed this).

Thanks, and again nice work!

Yup. That's correct. This checks logins and registrations. Therefore, you don't need to worry about past problems; if they are currently logging into multiple accounts, this will catch them. And yes, there are IP address options for registration.

[ricardoNJ]

Hi, This hack block a IP user and it show me in a thread (invisible for other, I guess) . My question is: Can I choose or create a thread for the notices that sent to me this hack go there? and how?

Thanks and I'm sorry for my bad english.

[Kiros72]

Originally Posted by ricardoNJ

Hi, This hack block a IP user and it show me in a thread (invisible for other, I guess) . My question is: Can I choose or create a thread for the notices that sent to me this hack go there? and how?

Thanks and I'm sorry for my bad english.

No problem

The threads that this modification creates are only private if the forum is private. In other words, if you set MADP to post threads in a public forum, they will be public. If you set it to post in a private forum, then only the people that have permission to view the forum will be able to see the thread.

Anyway, you can make the modification send you a private message instead of posting a thread. To do this, go to the Multiple Account Detection & Prevention Reporting options. You should see an option that will enable reporting by private messages. You have to enable it and you must enter your username (not your User ID) in the appropriate area.

If you need more help finding this option, let me know.

[exportforce]

After a month I yet again ask you:
Please enable an option that bans the first account too and also on multiple logins to ban both accounts automatically. In the last 3 weeks I am extremly encountering ppl that create up to 10 accounts and I can't even ban as fast as they create new accounts.

Please let US decide wether those should be banned too, for myself it is extremly urgent.

regards

[Kiros72]

Originally Posted by exportforce

After a month I yet again ask you:
Please enable an option that bans the first account too and also on multiple logins to ban both accounts automatically. In the last 3 weeks I am extremly encountering ppl that create up to 10 accounts and I can't even ban as fast as they create new accounts.

Please let US decide wether those should be banned too, for myself it is extremly urgent.

regards

Coding takes work. It won't happen if I just think about it. It takes work, and as of late, I've been doubly stressed because of final exams and graduate fiascoes. Now that I'm out of school, I should have two months of freedom (at least from scholastic activities).

Also, I never anticipated on releasing another 1.1.x version. The next planned release is 2.0.0, which incorporates database features and they are still of my highest priority. These database features are not easy to form. It's very complicated in the code, at least for me.

I do not have a release date planned. Just be patient and wait it out. If I do not have version 2.0.0 released within another month, I'll go ahead and work on one, last, 1.1.x version (1.1.4).

[exportforce]

If I pay you $20, will you implement this early ?
I don't know, but I think, that since you already "recognize" those, it can't be hard to activate it for us. I know that coding isn't easy, since I code bymyself a lot, but also some things are really important and if you would see my double, trippleaccounts you'd know how urgent it is for me.

[Kiros72]

Originally Posted by exportforce

If I pay you $20, will you implement this early ?
I don't know, but I think, that since you already "recognize" those, it can't be hard to activate it for us. I know that coding isn't easy, since I code bymyself a lot, but also some things are really important and if you would see my double, trippleaccounts you'd know how urgent it is for me.

Sure. Some support always helps, and because I appreciate such support, I'll go ahead and release a 1.1.4 version with the feature you've requested. I should have it out within a few days (a week at most).

[exportforce]

Originally Posted by Kiros72

Sure. Some support always helps, and because I appreciate such support, I'll go ahead and release a 1.1.4 version with the feature you've requested. I should have it out within a few days (a week at most).

As soon as you release that, please send me your Paypal-Adress via PM
I like to support, if it does help, and I really know that every $ helps in every way.
No more manual banning for first accounts, multiple login-accounts and stuff *drool*

big thanks in advance!

[Rideharder]

Warning: require_once([path]/madp/detection.php) [function.require-once]: failed to open stream: No such file or directory in [path]/includes/functions_login.php(185) : eval()'d code on line 3

Fatal error: require_once() [function.require]: Failed opening required '/home/kaplanfo/public_html/madp/detection.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/kaplanfo/public_html/includes/functions_login.php(185) : eval()'d code on line 3

I cant log in ..how can I remove this mod if I cant log back into my fourm?