"jwf" wrote:
> On Monday, March 9, 2015 at 11:38:00 AM UTC-4, Ant wrote:
>> "jwf" wrote:
>>> found this on a windows 7 computer and cannot find anything saying
>>> what it is used for.
>>>
>>> _!SHMSFTHISTORY!_
>>
>> Why were you looking for it and how did you find it?
>
> found it in a memory image during forensics analysis
Ok.
[snip]
Yes thanks, I know how to use search engines. What do you think I
based my comments about false positives on (when I mentioned side
effects)? All these results are hits from automatic analysis of
malware samples even when they appear not to be. That is quite obvious
to me as a malware researcher of some experience.
> BTW i did not find any references to any legit programs using this,
There's not much reason why you should. After all, these mutexes are
part of the internals of the Windows user interface, are undocumented
and not much use for anything else.
> which is the reasoning for my question. if you can find a reference
> to a legit program using this, then please let me know.
Of course I can and so should you if you're into forensic analysis
(look at the OS itself rather than Google). As I implied previously,
the malware references are red herrings and are caused by user
interface functions being called during the normal operation of the
executable. Note, malware may not display a user interface even when
written to run under the GUI subsystem as most are.
To be specific:
_!SHMSFTHISTORY!_ (shell microsoft history?)
Set/checked by shdocvw.dll "Shell Doc Object and Control Library"
_SHuassist.mtx (shell user assist mutex?)
Set/checked by browseui.dll "Shell Browser UI Library"
Both these DLLs are part of the OS and the mutexes get created when
certain shell functions to do with accessing the file system or the
web are called (I've made educated guesses as to the meaning of the
names). This is on XP and I doubt much has changed on Win 7. Any
programs legitimate or otherwise that make particular API calls will
cause the creation of these mutexes (MS calls them mutants).