this is happening only with latest version of vbulletin. in 3.7.2 it was not there...
it is because the 3.7.2 version did not had a hook where the system is now checking for that detail in the latest version of vBulletin, that's why you see that behavior now... but my first reply stand.