• Home
  • Blog
  • Online Scan
  • Update History
  • Online Scan: Analyze dism.exe file and fix runtime errors, Fix System Error
    Welcome to my blog. I found a malicious code that was added into the dism.exe file. Due to infection by malicious code, the file contents changed. The MD5 value of the infected file is: 551fdec732ef4c474690934bf326d485, and the file size is: 224 K ( 229,888 bytes )
    Risk level of malicious code
     
     
     
     
     
    ( 3 stars by 156 users )
    Behavior of malicious code ( 282 votes ) If you know more this malicious code, please vote. We sincerely hope you may share your information with other computer users and help them.
    1. Infect file
    12.06% (34)
    2. Intentionally destroy data
    9.93% (28)
    3. Steal personal privacy
    14.18% (40)
    4. Infect other computers through the Internet
    13.12% (37)
    5. Install the backdoor program so that the computer is controlled remotely
    14.18% (40)
    6. Cheat or threaten users to buy something
    13.12% (37)
    7. Download and install other programs without permission in the background
    12.77% (36)
    8. Pop up various advertisements and induce users to click
    10.64% (30)
    Binary Code Analysis:
    When the program runs, the PE loader will try to load the file to 0x01000000 in the virtual address space, Address Of Entry Point: 0x0001A2C0. This file has 5 SECTION.
    DOS Header
    DOS Stub
    ...
     
    NT File Signature
    NT HEADER
    FILE HEADER
     
    OPTIONAL HEADER
    Data Directory
    .text SECTION #1
    .data SECTION #2
    .rsrc SECTION #3
    .reloc SECTION #4
    ihokbij SECTION #5
    About this malicious code
    This malicious code is a 32-bit program that infects an EXE file. When the file is run or the file is loaded, the malicious code in the file is run first. Later, this malicious code also infects the following files:

    • dism.exe
    • dism.bmp.exe

    Tip: There is something I must emphasize. The file names listed above are infected by malicious code. It does not mean that all files named by these names are malicious files. It is inaccurate to determine whether a file is a malicious program based on its file name.

    The malicious code also infects files on the following path:

    • c:\windows\system32\eventproviders\sv-se\
    • c:\windows\system32\windowspowershell\v1.0\modules\netsecurity\nl\
    • c:\windows\chipset\
    • c:\windows\ssmaui wowee\xtras\
    • c:\windows\resources\themes\crystalaero\shell\crystala3\
    • c:\windows\corel\coreldraw graphics suite x5\programs\addons\docinfotool\
    • c:\windows\drivers\
    • c:\windows\system32\boot\ja-jp\
    • c:\windows\microsoft antimalware\definition updates\{cea61cca-85b7-4154-930a-32a69ca79694}\
    • c:\windows\system32\ne-np\
    • c:\windows\resources\themes\nude2\
    • c:\windows\temp\cr_d69ec.tmp\
    • c:\windows\assembly\nativeimages_v4.0.30319_64\cli.aspect.00834253#\3605bc36e012eda2ebf84efbd4fa4a95\
    • c:\windows\system32\ldt17_win32\
    • c:\windows\temp\7zs0dc39572\program files\panda security\panda cloud antivirus\drivers\nnsnahsl\x64_wvista\
    • c:\windows\temp\cr_990c1.tmp\
    • c:\windows\setup\seowon\program files\seowon\gdminit\
    • c:\windows\setup\seowon\system32\
    Tip: The code of most malicious files is fixed, rarely changed, which means, this type of malicious files regardless of which computer they are in, will copy themselves into the pre-set path, so we can go to the path listed above to find this file, and there is a great chance to find it.
    Are all the files with the same file name listed above and with the same path malicious files?
    Of course not. The file name is just the identification of the file. Strictly speaking, the file is modified by malicious code.

    The following are methods commonly used by malicious code in order to confuse users:

    • Deliberately modify their own file name to some system file name, or some well-known software name.
    • Generate malicious files in the system folder or in the installation folder of some well-known software, and even name their own folder with an antivirus software name (actually the user did not install this antivirus software). In fact, these malicious files are not system files, nor part of the famous software.

    For example, one of the most common system file names is: explorer.exe, and under normal circumstances, the system only has an explorer.exe process. When you open the Task Manager and find that there are two or more explorer.exe processes, it is likely the camouflage of some malicious viruses. As shown in the following figure, there are two explorer.exe processes in Task Manager.

    When I find the path where the file is located, it will be clear that the real explorer.exe system file is located under "C:\ Windows\", and the malicious file that pretends to be system process is under the other path.

    The running status of the dism.exe file that is infected with malicious code:
    dism.exe running statusTake up memory 132K
    Occupy CPU resources between 56% - 70%
    Run the program with the Administrator permissions.
    At runtime, 8 Windows system files, 0 external files (not owned by the Windows system), are called
    Windows system files
  • File name
  • Number of calling functions
  • ADVAPI32.dll
  • 27
  • KERNEL32.dll
  • 80
  • msvcrt.dll
  • 62
  • ntdll.dll
  • 3
  • USER32.dll
  • 3
  • ole32.dll
  • 4
  • OLEAUT32.dll
  • 11
  • VERSION.dll
  • 3
  • Not owned by the windows system
  • File name
  • Number of calling functions
  • In general, the most accurate way to determine if a file is a malicious file is to analyze its code and see what happens when these functions are called while the program is running. Does it have malicious behavior (destroying data or stealing data)? I have listed the functions called by this file and some internal data, but there is too much data, I can't show them all here. →Click here← to see the full binary code analysis page.
    dism.exe runtime behavior analysis
    The ADVAPI32.dll dynamic link library is loaded and the functions in the file are called: ( Advapi32.dll is part of a high-level API application interface service library that contains functions related to object security, registry manipulation, and event logging. It is generally located in the system directory: \WINDOWS\system32\ )
  • AdjustTokenPrivileges: The AdjustTokenPrivileges function enables or disables privileges in the specified access token.
  • LookupPrivilegeValueW: This function retrieves the locally unique identifier (LUID) used on a specified system to locally represent the specified privilege name.
  • OpenProcessToken: This function opens the access token associated with a process.
  • RegQueryValueExW: Retrieves the data associated with the default or unnamed value of a specified registry key.
  • RegOpenKeyExW: Opens the specified registry key. Note that key names are not case sensitive.
  • The KERNEL32.dll dynamic link library is loaded and the functions in the file are called: ( Kernel32.dll is a very important 32-bit dynamic link library file in the Windows operating system. It is a kernel-level file. It controls the system's memory management, data input and output operations and interrupt handling. When the Windows operating system starts, kernel32.dll resides in a specific write-protected area of memory, so that other programs cannot occupy this memory area. )
  • SetConsoleCtrlHandler: Adds or removes an application-defined HandlerRoutine function from the list of handler functions for the calling process.
  • SetErrorMode: Controls whether the system will handle the specified types of serious errors or whether the process will handle them.
  • GetStdHandle: Retrieves a handle to the specified standard device (standard input, standard output, or standard error).
  • GetConsoleMode: Retrieves the current input mode of a console's input buffer or the current output mode of a console screen buffer.
  • WriteConsoleW: Writes a character string to a console screen buffer beginning at the current cursor location.
  • GetModuleFileNameW: Retrieves the fully qualified path for the file that contains the specified module.
  • GetSystemInfo: Retrieves information about the current system.
  • CreateFileMappingW: Creates or opens a named or unnamed file mapping object for a specified file.
  • GetProcAddress: Retrieves the address of an exported function or variable from the specified dynamic-link library (DLL).
  • LoadLibraryW: Loads the specified module into the address space of the calling process. The specified module may cause other modules to be loaded.
  • GetModuleHandleExW: Retrieves a module handle for the specified module. The module must have been loaded by the calling process.
  • CreateFileW: Creates or opens a file or I/O device. The most commonly used I/O devices are as follows: file, file stream, directory, physical disk, volume, console buffer, tape drive, communications resource, mailslot, and pipe. The function returns a handle that can be used to access the file or device for various types of I/O depending on the file or device and the flags and attributes specified.
  • UnhandledExceptionFilter: An application-defined function that passes unhandled exceptions to the debugger, if the process is being debugged.
  • TerminateProcess: Ends the calling process and all its threads.
  • GetSystemTimeAsFileTime: Retrieves the current system date and time. The information is in Coordinated Universal Time (UTC) format.
  • GetCurrentProcessId: Retrieves the process identifier of the calling process.
  • GetTickCount: Retrieves the number of milliseconds that have elapsed since the system was started, up to 49.7 days.
  • QueryPerformanceCounter: Retrieves the current value of the performance counter, which is a high resolution (<1us) time stamp that can be used for time-interval measurements.
  • GetModuleHandleA: Retrieves a module handle for the specified module. The module must have been loaded by the calling process.
  • SetUnhandledExceptionFilter: Enables an application to supersede the top-level exception handler of each thread of a process.
  • InterlockedCompareExchange: Performs an atomic compare-and-exchange operation on the specified values.
  • InterlockedExchange: Sets a 32-bit variable to the specified value as an atomic operation.
  • SetEvent: Sets the specified event object to the signaled state.
  • GetCurrentThreadId: Retrieves the thread identifier of the calling thread.
  • GetModuleHandleW: Retrieves a module handle for the specified module. The module must have been loaded by the calling process.
  • GetCurrentProcess: Retrieves a pseudo handle for the current process.
  • GetLastError: Retrieves the calling thread's last-error code value.
  • The following files have been identified as malicious files. Some files are variants of dism.exe; some files are another type of malicious file, but use the same file name as dism.exe.

    It is a simple and effective way to determine whether a file is a malicious file by a hash value, which has lower false detection rate than the "static signature" method. So, if the MD5 value of a file on the computer is the same as the MD5 value listed below, then it is sure that the file is a malicious file.

    This is my analysis results to the code of each malicious below, mainly provided to industry professionals who engage in the maintenance of computer security. If you are interested, you can also have a view, but it may require certain computer knowledge.
    • File Md5
    • File Size
    • File Bit
    • File Type
    • Binary Code Analysis

    How to repair or remove dism.exe

    Method 1: Manual Removal

    • Reboot the system and then enter safe mode (Click here to see how each Windows version (XP/Vista/7/8/10) goes into safe mode)

    • Open Task Manager and if dism.exe is running, end this program.
    dism.exe running status

    • Show all hidden files.
    Step: "My Computer" -> "Floder Options" ->"View" -> "Show hidden files, folders, and drives"

    • Malicious code used to generate or infect files on the following paths, so you need to one by one go into the following path, and delete all files [  dism.exe, dism.bmp.exe  ]

    • c:\windows\system32\eventproviders\sv-se\
    • c:\windows\system32\windowspowershell\v1.0\modules\netsecurity\nl\
    • c:\windows\chipset\
    • c:\windows\ssmaui wowee\xtras\
    • c:\windows\resources\themes\crystalaero\shell\crystala3\
    • c:\windows\corel\coreldraw graphics suite x5\programs\addons\docinfotool\

    • Finally, restart your computer.

    Method 2: Automatic Removal Using Tools (Recommended)

    This is free virus detection software, and it can be well compatible with many well-known anti-virus software, so users do not have to uninstall anti-virus software on the computer.

    It is "environmentally friendly" for computers. After downloading, it can be used by decompression and without installation. In the process of running, it will not write any information to the registry, nor create any new files to the Windows folder of the system disk. When you do not need it, you can delete it. It will not leave any spam information on your computer.

    When you find your operating system is abnormal, and the file name listed above appears in the Task Manager, or there are several processes in running with the same name as the core file name, it is best to download the anti-virus software to check your system.

    Online detection of dism.exe

    If you don't know if dism.exe is infected with malicious code on your computer, you may also use online scan tool.

    • Use the following online detection function to check the file.
  • • Enter the file name, or file MD5, for the query.
  • • You can also scan a file online. Click the "Upload File" button, and then click the "submit" button, to immediately detect whether the file is a virus. (Tip: The maximum size of the file uploaded cannot exceed 8MB)
  • How do I use the T21 engine for online scanning?

    T21 can detect unknown files online, mainly using "behavior-based" judgment mechanism. It is very simple to use T21.

    1. Click the "Upload File" button, select the file you want to detect, and then click "Submit".
    2. The next step is to wait for the system to check, which may take a little time, so please be patient.
    3. When the T21 scan engine finishes detection, the test results are immediately fed back, as shown below:

    • If you suspect that there are malicious files on your computer, but you cannot find where they are, or if you want to make a thorough check on your computer, you can download the automatic scanning tool.

    If you want to know what kind of T21 system is, you can click here to view the introduction of T21. You can also go to the home page to read the original intention and philosophy of my development of T21 system.

    Other captured malicious files:
    dfrgui.exe file analysis
    dismhost.exe file analysis
    diskraid.exe file analysis
    djoin.exe file analysis
    dispdiag.exe file analysis
    dllhst3g.exe file analysis
    patch.exe.112978.gzquar file analysis
    qtsolutions_service-head.dll file analysis
    foxitconnectedpdfservice.exe file analysis
    Copyright statement: The above data is obtained by my analysis, and without authorization, you may not copy or reprint it.
    Leave a Reply

    Your email address will not be published. Required fields are marked *
    If you need help, please leave a message, try to match the picture, and I will reply as soon as possible to each question.

    Name *

    Email

      Comment
      ToolBar:
    Preview, Read Only, Click here Edit Post.

    Copyright © 2016-2019 mygoodtools.com All rights reserved.