The snippet is then executed via Asynchronous Procedure Call (NtQueueApcThread). Just looking at the size of the payload and the strings made me curious enough so I decided to have a quick look at the code.<\/p>\n Turns out, this little snippet doesn’t like Shell_NotifyIconW API very much and it patches it in a very clever and selective way.<\/p>\n The disassembled code of the main routine from the snippet looks like this:<\/p>\n The PatchShell_NotifyIconW<\/strong> function shown on the screenshot is responsible for allocating a small buffer in memory (via ZwAllocateVirtualMemory) that will hold a code of the function modifying the standard behavior of Shell_NotifyIconW API.<\/p>\n As per MSDN, the Shell_NotifyIconW<\/a> function takes 2 arguments:<\/p>\n The new function installed by ZeroAccess looks like this:<\/p>\n The 33333333h is an address (patched at run-time) to the old unpatched version of the function, so that once ZeroAccess modifies the function’s behavior it can pass the control back to the original function.<\/p>\n As you can see, the patch is simple – it only modifies a dwMessage<\/strong> value so that it is always equal to NIM_DELETE<\/strong>, which pretty much means that any attempts to add\/modify\/change status of an icon on the notification area (tray) will fail.<\/p>\n While I have not tested it as I don’t have any image with all these security settings on, it seems to be a simple trick to prevent the ‘annoying’\u00a0 security notifications from happening while the malware is doing its evil thing. This is indirectly confirmed by the way the actual patch occurs. Instead of patching the entry code of Shell_NotifyIconW in a typical, process-global detour-like fashion, the malware walks through all DLLs loaded into Windows Explorer and finds addresses of Shell_NotifyIconW function only within the Import Address Tables\u00a0 of two DLLs: ActionCenter.dll<\/a> and wscntfy.dl<\/a>l. These hold the code responsible for the system\/tray icon area notifications related to current security state of the system.<\/p>\n Quite frankly, I like this piece of code as it is very neatly written (it even self-removes itself from memory after it is executed) but more importantly, these popups are actually quite annoying! \ud83d\ude42<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" There is a lot of ZeroAccess analysis all over the place, so not sure if anyone documented it before, but oh well…\u00a0 here it goes… I have been recently looking at a new sample of ZeroAccess and spotted that at … Continue reading ![\"\"](\"https:\/\/www.hexacorn.com\/blog\/wp-content\/uploads\/2012\/09\/ZeroAccess_Shell_NotifyIconW_1-300x149.png\" "\\"ZeroAccess_Shell_NotifyIconW_1\\"")
<\/a><\/p>\n![\"\"](\"https:\/\/www.hexacorn.com\/blog\/wp-content\/uploads\/2012\/09\/ZeroAccess_Shell_NotifyIconW_2-250x300.png\" "\\"ZeroAccess_Shell_NotifyIconW_2\\"")
<\/a><\/p>\nBOOL Shell_NotifyIcon(\r\n\u00a0 _In_\u00a0 DWORD dwMessage,\r\n\u00a0 _In_\u00a0 PNOTIFYICONDATA lpdata\r\n);<\/pre>\n
![\"\"](\"https:\/\/www.hexacorn.com\/blog\/wp-content\/uploads\/2012\/09\/ZeroAccess_Shell_NotifyIconW_31-300x41.png\" "\\"ZeroAccess_Shell_NotifyIconW_3\\"")
<\/a><\/p>\n