It's a security hole - I found it out quite by accident before I realised what I had done.
The symptoms that the
OP experienced are consistent with this being a "war" between him and this "hacker", as his attempts to reconnect would have booted the hacker, and vice versa.
Clearly though, it would be necessary for this hacker to have access to both the account number and password, easily done by accessing the registry of the host machine via a compromised wireless network. It may also be possible if the breach allowed the remote execution of code on the host machine, but running the session display elsewhere.
This password should be considered compromised, and possibly ALL casino passwords on that machine.These should ALL be changed RIGHT NOW, and efforts made to secure the wireless network against this.
The machine then needs to be swept thoroughly for malware, and if found, the passwords should be all changed a second time once the machine has been fully cleaned up (in case the malware has been used to obtain these also).
Knowing the account numbers is less of a problem, certainly some casinos think so, as they publish the full account number of prizewinners, rather than just the outer characters, as well as first name and initial of surname.
MG casinos should NOT allow a newer session to boot off an existing session, it should be that an existing session should prevent the creation of a new session, and it should be up to support to log out a "stuck" session after verifying the details of the customer. Sessions that end up "stuck" should also have a default timeout, so that an open session does not sit vulnerably on the casino server if the local client machine loses the ability to establish contact.
Bookmarks