It might just be me thinking aloud, but looking at the pic, is sneaky not set to no login locally or externally, therefore account has no rights to do anything.
I could be wrong though, as I’m doing this from memory and not looking at computer.
Also, I would need to check but the only difference to stand out is is site import as been as the common factor. I’ll test this when I’m back to see.
Unfortunately I didn’t try to do anything when I found, just deleted immediately. I’m happy, our servers are not compromised it was only a bit frightening
IW-Robert has just confirmed it is created due to siteworx import. Those guys rock.
Robert asked 1 question which thinking about it, should have been the first questioned asked, can you do anything with sneaky when logged in.
I tried a few things but was always access denied due to no commands for sneaky.
If you find you can, please open a support ticket with IW
It’s going to be brought up at next dev meeting though, so hopefully maybe set to auto delete sneaky.
Finally, as you all know, it is safe to delete the account sneaky.
I hope that helps a little
Many thanks
John[/QUOTE]
I also just found the “sneaky” user on some, but not all, of my servers. I was a bit worried as well. I am opening a ticket to request the next InterWorx upgrade remove lingering “sneaky” users. Anyone with access to the server, via a firewall misconfiguration or a SiteWorx account, has access to a password-less user with the SUPER privilege. At the least the user should be created with a random password even during an import.