• Home
  • Blog
  • Online Scan
  • Update History
  • Online Scan: Analyze wplugin.dll file and fix runtime errors, Fix System Error
    Welcome to my blog. I found a malicious code that was added into the wplugin.dll file. Due to infection by malicious code, the file contents changed. The MD5 value of the infected file is: 8847a8302dacc1d6fca61f125c8fe8e0, and the file size is: 108 K ( 110,592 bytes )
    Risk level of malicious code
     
     
     
     
     
    ( 4 stars by 141 users )
    Behavior of malicious code ( 284 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
    14.08% (40)
    2. Intentionally destroy data
    12.32% (35)
    3. Steal personal privacy
    10.56% (30)
    4. Infect other computers through the Internet
    14.44% (41)
    5. Install the backdoor program so that the computer is controlled remotely
    12.68% (36)
    6. Cheat or threaten users to buy something
    13.03% (37)
    7. Download and install other programs without permission in the background
    11.97% (34)
    8. Pop up various advertisements and induce users to click
    10.92% (31)
    Binary Code Analysis:
    When the program runs, the PE loader will try to load the file to 0x10000000 in the virtual address space, Address Of Entry Point: 0x0000DD33. This file has 5 SECTION.
    DOS Header
    DOS Stub
    ...
     
    NT File Signature
    NT HEADER
    FILE HEADER
     
    OPTIONAL HEADER
    Data Directory
    .text SECTION #1
    .rdata SECTION #2
    .data SECTION #3
    .rsrc SECTION #4
    .reloc SECTION #5
    About this malicious code
    This malicious code is a 32-bit program that infects an DLL 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:

    • wplugin.dll
    • wplugin.jpg

    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\
    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.

    At runtime, 6 Windows system files, 0 external files (not owned by the Windows system), are called
    Windows system files
  • File name
  • Number of calling functions
  • KERNEL32.dll
  • 99
  • ADVAPI32.dll
  • 8
  • SHELL32.dll
  • 1
  • WS2_32.dll
  • 19
  • iphlpapi.dll
  • 1
  • SHLWAPI.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.
    Export function:
    The following function is a function provided by this file. The export function is useful for analyzing the specific behavior of a runtime file, starting from the function entry address, and debugging the code line by line. You can get a lot of data generated by this file.
    Export File - DLLTest.dll
  • Ordinals
  • Function Name
  • Entry Address
  • 0x00000001
  • HandleCode
  • 0x00001336
  • wplugin.dll runtime behavior analysis
    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. )
  • GetProcAddress: Retrieves the address of an exported function or variable from the specified dynamic-link library (DLL).
  • 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.
  • LoadLibraryA: Loads the specified module into the address space of the calling process. The specified module may cause other modules to be loaded.
  • SetFileTime: Sets the date and time that the specified file or directory was created, last accessed, or last modified.
  • CreateThread: Creates a thread to execute within the virtual address space of the calling process.
  • WaitForSingleObject: Waits until the specified object is in the signaled state or the time-out interval elapses.
  • SetThreadPriority: Sets the priority value for the specified thread. This value, together with the priority class of the thread's process, determines the thread's base priority level.
  • GetCurrentProcessId: Retrieves the process identifier of the calling process.
  • Process32Next: Retrieves information about the next process recorded in a system snapshot.
  • Process32First: Retrieves information about the first process encountered in a system snapshot.
  • CreateToolhelp32Snapshot: Takes a snapshot of the specified processes, as well as the heaps, modules, and threads used by these processes.
  • TerminateThread: Terminates a thread.
  • GetModuleFileNameA: Retrieves the fully qualified path for the file that contains the specified module.
  • GetModuleHandleA: Retrieves a module handle for the specified module. The module must have been loaded by the calling process.
  • GetLastError: Retrieves the calling thread's last-error code value.
  • FlushFileBuffers: Flushes the buffers of a specified file and causes all buffered data to be written to a file.
  • GetEnvironmentStringsW: Retrieves the environment variables for the current process.
  • RtlUnwind: Initiates an unwind of procedure call frames.
  • ExitProcess: Ends the calling process and all its threads.
  • GetCurrentThreadId: Retrieves the thread identifier of the calling thread.
  • TlsSetValue: Stores a value in the calling thread's thread local storage (TLS) slot for the specified TLS index. Each thread of a process has its own slot for each TLS index.
  • TlsAlloc: Allocates a thread local storage (TLS) index. Any thread of the process can subsequently use this index to store and retrieve values that are local to the thread, because each thread receives its own slot for the index.
  • TlsGetValue: Retrieves the value in the calling thread's thread local storage (TLS) slot for the specified TLS index. Each thread of a process has its own slot for each TLS index.
  • SetUnhandledExceptionFilter: Enables an application to supersede the top-level exception handler of each thread of a process.
  • TerminateProcess: Ends the calling process and all its threads.
  • GetCurrentProcess: Retrieves a pseudo handle for the current process.
  • GetStdHandle: Retrieves a handle to the specified standard device (standard input, standard output, or standard error).
  • GetStartupInfoA: Retrieves the contents of the STARTUPINFO structure that was specified when the calling process was created.
  • FreeEnvironmentStringsA: Frees a block of environment strings.
  • FreeEnvironmentStringsW: Frees a block of environment strings.
  • 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\ )
  • CryptReleaseContext: The CryptReleaseContext function releases the handle of a cryptographic service provider (CSP) and a key container.
  • CryptAcquireContextA: The CryptAcquireContext function is used to acquire a handle to a particular key container within a particular cryptographic service provider (CSP). This returned handle is used in calls to CryptoAPI functions that use the selected CSP.
  • GetUserNameA: Retrieves the name of the user associated with the current thread.
  • The following files have been identified as malicious files. Some files are variants of wplugin.dll; some files are another type of malicious file, but use the same file name as wplugin.dll.

    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 wplugin.dll

    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)

    • 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 [  wplugin.dll, wplugin.jpg  ]

    • c:\windows\

    • Finally, restart your computer.

    Method 2: Automatic Removal Using Tools (Recommended)

    1. Download Removal Tool

    2. Save it into your computer and install it step by step.

    3. During the installation process, the user interface is available in multiple languages and is easy to use.

    4. The installation process is an online installation, so after the installation is complete, the software version and virus database are up-to-date.

    5. After the installation is complete, run the antivirus software and click the "Scan Computer Now!" button to scan the whole system.

    6. Tick "Select all" and then Remove to delete all threats. Reboot 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 wplugin.dll

    If you don't know if wplugin.dll 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:
    aeadisrv.exe file analysis
    smax4pnp.exe file analysis
    ws2help.dll file analysis
    dnlauncher.exe file analysis
    chcfg.exe file analysis
    kb888111srvrtm.exe file analysis
    dopdf.exe file analysis
    intel_opencl_icd32.dll file analysis
    ocl_cpu_intelopencl32.dll 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.