Administrative and Maintenance Tools - Multiple account login detector (AE Detector)

Mod of the Month winner!
Top 10 most installed mods for vB3.6!

Same plug-in found here:

https://vborg.vbsupport.ru/showthread.php?t=107566

There are no differences as this plug-in works with both 3.5 and 3.6 versions of vBulletin.

If you are like me and migrated from .threads, a common modification was an "AE detector", a simple mod that saved a cookie of a history of ids logged into on your site. If someone logged into more than one account, you got a PM letting you know that your site was being accessed from multiple accounts.

Over the years this was very helpful in identifying users who were posting under multiple accounts (alter-egos!) and users who would return after being banned.

You might be wondering why I don't use the vbcookie call - well, thats because on logout all vB cookies are cleared, so we need to store a cookie that is not effected by the login/logout process.

New Installation
1. Add New Product with attached XML
2. Go to vBulletin Options -> AE Multiple Login Detection Settings and set your specific settings.

Time to install: Easy - 2 minutes.

Upgrade
If you installed this as a Plug-in manually, you can delete that plugin and install this Product, just make sure to go into the Options and set them accordingly.

I hope you find this useful and will click INSTALL if you use it; should it prove useful to enough people I can look at making this installation more automated without the need for edits and an Admin Options page.

To upgrade you will want to reimport this XML file and edit your options accordingly.

1.0.3
-----
. Added a check to ensure that users weren't deleted when reporting violations
. added htmlspecialchars_uni call to username

Note: I am unable to get the call to construct_phrase with $vbphrase['multiplelogin_alert'] to work reliably, as such the $message variable is still set manually inside the plug-in and not via the phrase. If anyone has an idea of why this might not always work, I'm all ears.

1.0.2
-----
. Updated to include exclusion groups, users
. Changed so PM is sent by ae sender id

1.0.1
-----
. Released as a Product (thank you PHPGeek2k3 for your help)
. Added option to post to a forum versus send a PM (or both)
. All settings moved into Admin Option

1.0.0
-----
Initial release.

[Boofo]

Look at the code.

[FRANKTHETANK 2]

Originally Posted by Mum

Just a small question, how do we know that it WASN'T this mod?

I know it was this hack because i have known this guy for 9 years and he lives 5 blocks from me. Look at the aim conversation that him and me had he says it right there. That should be fact enough for any one to investigate it.

[vitrag24]

This mod is working perfact on vbulletin 3.7.1 [checked creating thread option - not checked pm function as i don't use it.]

[MPDev]

There is only one query in this mod; it's used to grab a username for formatting on the post itself. The query is protected by checking for a NULL value and a is_numeric value. If someone were to try an injection, these two checks would prevent it.

What *can* be done is someone can mess with the cookie to make it look like they are logging into a ton of accounts - if they want to throw a ton of userids into the cookie, they can. AE Detector will simply report what's stored in the cookie.

Never say never, but this plug-in contains very little code and only one query to the vB user database.

[Boofo]

Well, I'll say never as to this not being the way in that hacker used on his site.

Welcome back, sir.

[Paul M]

Originally Posted by FRANKTHETANK 2

I might even get the owner of the server i was on to come and back me up. Not only did he have access to my site, but he deleted cpanel, he messed up whmcs, and he replaced every and i mean ever index.php/html/etc, on the server.

I have no doubt that someone may have done that to you - but not via this modification. Its simply not possible.

[Mum]

Originally Posted by MPDev

There is only one query in this mod; it's used to grab a username for formatting on the post itself. The query is protected by checking for a NULL value and a is_numeric value. If someone were to try an injection, these two checks would prevent it.

What *can* be done is someone can mess with the cookie to make it look like they are logging into a ton of accounts - if they want to throw a ton of userids into the cookie, they can. AE Detector will simply report what's stored in the cookie.

Never say never, but this plug-in contains very little code and only one query to the vB user database.

Thank you MPDev

[johnban]

Hi Guys,

sorry for posting that here but I have posted it from 17th to "Multiple Account Registration prevation" and I had no answer so far.

So I am posting it again here in case you can tell my why.

thanks in advance.

Hi I installed the hack in 3.7

If I have a user that has logged in and then he is making a new registration then the hack it's catching him.

But ??..

One user has registered into my forum at 16:00 (let?s say) from IP address 11.111.111.111 (of course it is not the real IP). After 30 minutes he is registering again with different username/mail but from the same IP. Shouldn?t be captured by the hack ??

Thanks,

John B.

[Videx]

Originally Posted by johnban

from the same IP. Shouldn?t be captured by the hack ??

Yes, that would be nice. But if he's trying to avoid getting caught via cookie he can just clear his cookies. Or he could use a different computer.

It's probably not real unusual for us to have a husband & wife discover our forum and register from the same IP within minutes of each other, but on their own computers.

Note also as I've pointed out, there's some other mod or something out there disabling this mod. It's working good on one of my forums, but not the other.

[FRANKTHETANK 2]

listen not only can he log in to my account he can edit anything he wants. He can sign into my name and be full admin.