This sounds like a false positive to me. Unless //echo -a $com(0) is reporting something other than 0, mIRC is unable to perform any keylogging without dlls/coms running, so it really can't be due to a compromised client. The md5 matches up with the correct value for 6.35, so for all intensive purposes mIRC is running perfectly normally.
