I just did a quick check of things and tested these fields related to this functionality from a programming point of view, and couldn't find anything obviously wrong that would be causing such an error.

Therefore it seems the most likely culprit is that someone has your password and you should change it to be safe. If it continues to happen after changing your password, please let me know.

I'll also keep an eye on these fields in my own profile and that of a test account to see if they change on their own.

DocJohn