Post Fri May 23, 2008 6:21 am

Injecting Browser Helper Objects Remotely == ?

Some system monitoring program gave me this message
A new startup program has been detected
D:\windows\system32\jkhfd.dll,c

which means that it is executing the function whose name is c which is exported by jkhfd.dll

I dissassembled the file(jkhfd.dll) and found the following list of exported functions-
c
DllCanUnloadNow
DllGetClassObject
f
InitSecurityInterfaceWLsaApCallPackage
LsaApCallPackagePassthrough
LsaApCallPackageUntrusted
LsaApInitializePackage
LsaApLogonTerminated
LsaApLogonUser
LsaApLogonUserEx
o
s
SpInitialize

(the function c, as I suspected, is exported)

Some sysinternals tools told me that the above dll is there(injected?) as the browser helper objects
HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Browser Helper Objects
{B2CEFDCD-4318-4FD1-B87F-3E28D54ECF8D} d:\windows\system32\jkhfd.dll


From the above list of exported functions, most are implemented by the dll creator herself. But the win32 function(s) like LogonUser(which attempts to logon,probably remotely) has aroused my suspicion.

My questions-

Since the dissassembler can't locate the functions in the dissassembly, please suggest some other way of reversing the dll ?
Any further info on this method of attack, that is, how can someone remotely inject BHOs(browser helper objects) into my browser ?
There is no rule, law or tradition that apply universally... including this one.