I have just come across a .dll in my startup list that has me baffled and a bit concerned as to just what it is. In the past, a Google search has always provided something on any file name I have ever checked, but this one returns zip.
The name is hurwenf.dll
In msconfig the startup item is listed simply as hurwenf, with the command being C:\WINDOWS\system32\rundll32.exe C:\WINDOWS\system32\hurwenf.dll,uyesscc
In looking at it's properties it only declares association to an unknown program.
I did a basic files/folders search for all instances of hurwenf, and again looking for the phrase uyesscc. All that was returned was the .dll itself, present in the Windows/system32 folder, and 2 referenced files found in an orphaned program folder belonging to a long-removed spyware detection/removal program, SpyHunter, which I had likely tried out and quickly removed. One file is a support log, which merely lists the item as being one of the items in normal startup. The other I'm unfortunately a bit vague on except for recalling it as an xml file, or having seen xml in the name. When I could find no valid reason for this dll to be in action, I turned it off in msconfig and rebooted to see if any of my programs had any problems without it. Only then did I think to go back and examine the "xml" file further, discovering it had now disappeared. Restoring startup status to the unknown dll and re-starting in hopes it would also re-initiate the mystery file did not work as I thought it might; the file has not returned, leaving only the support log. Obviously since it vanished into thin air it could not have been an xml, and I'm smacking my head on the desk for having failed to not have at least jotted the full name down before making any changes; it didn't occur to me this file would go "poof" as it did.
Attempting decompile on a copy of the dll fails stating it was not built with VB 5 or 6, so I do not have a way to do this.
In opening the dll with Notepad the one only discernable reference I found reads:
hurwenf.dll DllCanUnloadNow DllGetClassObject DllRegisterServer DllUnregisterServer uyesscc
The one potential clue to it's origin/nature that strikes me is maybe held in the disappearance of the mystery file; could this suggest that hurwenf.dll was a leftover of the SpyHunter program, rather than part of something SpyHunter tagged as an invader?
Any info or suggestions would be greatly appreciated; I won't rest easy until knowing just what the devil this thing is.