• Home
  • Blog
  • Online Scan
  • Update History
  • Online Scan: Analyze rtlupd.exe file and fix runtime errors, Fix System Error
    Welcome to my blog. I found a malicious code that was added into the rtlupd.exe file. Due to infection by malicious code, the file contents changed. The MD5 value of the infected file is: 253173e6754b98282edcf0c281a38709, and the file size is: 1.5 MB ( 1,545,891 bytes )
    Risk level of malicious code
     
     
     
     
     
    ( 3 stars by 141 users )
    Behavior of malicious code ( 268 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
    9.7% (26)
    2. Intentionally destroy data
    12.69% (34)
    3. Steal personal privacy
    10.45% (28)
    4. Infect other computers through the Internet
    13.06% (35)
    5. Install the backdoor program so that the computer is controlled remotely
    9.33% (25)
    6. Cheat or threaten users to buy something
    13.06% (35)
    7. Download and install other programs without permission in the background
    15.67% (42)
    8. Pop up various advertisements and induce users to click
    16.04% (43)
    Binary Code Analysis:
    When the program runs, the PE loader will try to load the file to 0x00400000 in the virtual address space, Address Of Entry Point: 0x0017C514. This file has 4 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
    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:

    • rtlupd.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:\dbz6675b\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_d64f941046b33a97\
    • c:\drivers\audio\j4pj1\wdm\
    • c:\acer\empowering technology\erecovery\autorun\sw1\audio\wdm\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_a9dd3462d2552c4c\
    • c:\drivers\alc1200_audio_v6015859_windows7\vista\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_84e02ba6ce4026c8\
    • c:\swsetup\sp74867\vista\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_570eb3c03e8192be\
    • c:\compaq\audio\
    • c:\drivers\win\audio\vista\
    • c:\swtools\drivers\audio\realtek\vista\
    • c:\windows\system32\driverstore\filerepository\hdasgma4.inf_x86_neutral_039094c57bbaef91\
    • c:\swsetup\drv\audio\realtek\ccg1.xrea_llnmb2\6.0.1.7584\src\vista\
    • c:\etiquetas\cybersineslda\software\softetpos\dvdetpos\dvdetposlibra\6215\win 7\audio\setup\vista\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_585e3cdad574b0c9\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_3fab0d067a87c5ce\
    • c:\dell\drivers\rkktf\vista\
    • c:\dell\drivers\rkktf\wdm\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_b95248914b096303\
    • c:\windows\system32\driverstore\filerepository\hdahpbpc.inf_x86_neutral_5877c1ddd55aeefc\
    • c:\program files\realtek\audio\installshield\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_0059ecc9bc3d4289\
    • c:\swsetup\sp83861\win32\
    • c:\dell\drivers\r245244\vista\
    • c:\windows.old\windows\drivers\exe\audio driver (realtek)\vista\
    • c:\swsetup\sp75973\win32\
    • c:\drivers\realtek audio driver\vista\
    • c:\dell\drivers\r282239\wdm\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_c5a556001052dd65\
    • c:\swsetup\drv\audio\realtek\hrm1.xrea_rr0lb2\6.0.1.8105\src\win32\
    • c:\dell\drivers\r282239\vista\
    • c:\swtools\drivers\audio\realtek\wdm\
    • c:\swsetup\drv\audio\realtek\jl1.xreal_qqjdb2\6.0.1.8110\src\win32\
    • c:\swsetup\drv\audio\realtek\sr2.xreal_ppwab2\6.0.1.7977\src\win32\
    • c:\d\s\r2\
    • c:\drivers\audio.realtek\hda\r2.53\
    • c:\windows\system32\driverstore\filerepository\hdalc.inf_x86_neutral_b5a228affa4a7ed0\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_7feb047adaf7dfb5\
    • c:\windows\system32\driverstore\filerepository\hda.inf_x86_neutral_2533e288018747af\
    • c:\swsetup\sp78234\win32\
    • c:\mydrivers\backup\backup\drivers\realtek high definition audio\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_c2070fa5dcf5761c\
    • c:\swsetup\drv\audio\realtek\sptp1.xre_nn5gb2\6.0.1.7801\src\win32\
    • c:\etiquetas\cybersineslda\software\softetpos\dvdetpos\dvdetposlibra\sp-1000c\20101210_winxp\x86\x86\audio\wdm\
    • c:\windows\system32\driverstore\filerepository\hda861a.inf_x86_neutral_c5a36d862ffafedc\
    • c:\dell\drivers\r274720\wdm\
    • c:\swsetup\drv\audio\realtek\cwby1.xre_qqlsb2\6.0.1.8090\src\win32\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_c87e40578a7b602f\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_e49c908894de4a24\
    • c:\program files\realtek\audio\hda\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_d2f0c099c4dab695\
    • c:\esupport\edriver\software\audio\realtek\vista\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_2c59f34271e749c4\
    • c:\drivers\audio\realtek\hda\
    • c:\swsetup\sp74368\vista\
    • c:\swsetup\audio_realtek\vista\
    • c:\swsetup\sp75531\win32\
    • c:\swsetup\drv\audio\realtek\ce1.xreal_nn3ub2\6.0.1.7898\src\win32\
    • c:\swsetup\drivers\audio\vista\
    • c:\windows\system32\reinstallbackups\0022\driverfiles\
    • c:\swsetup\drv\audio\realtek\fp1.xreal_nn4cb2\6.0.1.7756\src\win32\
    • c:\drivers\gigabyte mobo\audio\realtek\hd_audio\vista\
    • c:\windows\system32\driverstore\filerepository\hdahpbpc.inf_x86_neutral_e2e9cb3cd4ea07b9\
    • c:\drivers\asrock mobo\drivers\audio\realtek\win7-64_win7_vista64_vista_xp64_xp(r266)\wdm\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_15ade80e1e30fca8\
    • c:\swsetup\sp62310\vista\
    • c:\windows\system32\driverstore\filerepository\hdart4.inf_x86_d829290a6b77a915\
    • c:\drv\audio\win32\
    • c:\windows\system32\driverstore\filerepository\hdacpc.inf_x86_neutral_60978d7617c8bd49\
    • c:\drivers\gigabyte ga-73pvm-s2h\audio\realtek\hd_audio\vista\
    • c:\swsetup\sp38497\wdm\
    • c:\windows\system32\driverstore\filerepository\hdacpc.inf_x86_neutral_066a838095ed22a0\
    • c:\windows\system32\driverstore\filerepository\hdahpbpc.inf_x86_neutral_0a95480833ad5a24\
    • c:\swsetup\sp62310\wdm\
    • c:\drivers\asrock mobo\drivers\audio\realtek\win7-64_win7_vista64_vista_xp64_xp(r266)\vista\
    • c:\swsetup\drv\audio\realtek\ce1.xreal_nn3ub2\6.0.1.7818\src\win32\
    • c:\swsetup\drivers\audio_kk\vista\
    • c:\windows\system32\driverstore\filerepository\hdamaxxd.inf_x86_neutral_9a5addff18019054\
    • c:\windows\system32\driverstore\filerepository\hdasgma4.inf_x86_neutral_aebce2e381a8c5e8\
    • c:\swsetup\sp74726\vista\
    • c:\compaq\audio\realtek\wdm\
    • c:\swsetup\drv\audio\realtek\ce1.xreal_nn3ub2\6.0.1.7743\src\vista\
    • e:\windows\system32\drvstore\hdart_766d400462c3514fcd5ca6f0ea01746ac95d7bfe\
    • c:\windows\
    • c:\swsetup\sp78936\win32\
    • c:\drivertemp\36324195812\hdaudiofunc_01&ven_10ec&dev_0283\win32\
    • c:\acer\empowering technology\erecovery\autorun\sw1\audio\vista\
    • c:\swsetup\drv\audio\realtek\jl1.xreal_qqjdb2\6.0.1.8083\src\win32\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_01adabcc718c485b\
    • c:\archivos de programa\realtek\audio\drivers\
    • c:\windows\system32\driverstore\filerepository\hdasrsa.inf_x86_f966c72b9c3fa97c\
    • c:\windows\system32\driverstore\filerepository\hdartgi.inf_x86_neutral_8c081a2cc2c1e8c5\
    • c:\drivers\audio.realtek\hda\new\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_eb8c3358c3af8758\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_5373149122537d5a\
    • c:\swsetup\drv\audio\realtek\pp1.xreal_nn1ab2\6.0.1.7750\src\vista\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_9032b0b770e3a75a\
    • c:\windows\system32\driverstore\filerepository\hdacpc.inf_0af0d25d\
    • c:\swsetup\drv\audio\realtek\pmd1.xrea_qqqpb2\6.0.1.8135\src\win32\
    • c:\etiquetas\cybersineslda\software\softetpos\dvdetpos\dvdetposlibra\sp-1000c\20101213_win7\x86\x86\audio\vista\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_3f44e43f63f95017\
    • c:\drivers\realtek high definition audio driver\wdm\
    • c:\oemdrv\2\
    • c:\drivers\audio.realtek\hda\r2.61\
    • c:\drivers\audio\
    • c:\drivers\audio\j4pj1\vista\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_1e166ca5276e5e68\
    • c:\swsetup\sp72594\vista\
    • c:\swsetup\drv\audio\realtek\sptp1.xre_nn5gb2\6.0.1.7770\src\win32\
    • c:\drivers\realtek audio driver\win32\
    • c:\downloads\emachine et-1810 drivers\audio_realtek_6.0.1.5898 w7x86x64\vista\
    • c:\drivers\gigabyte ga-73pvm-s2h\audio\realtek\hd_audio\wdm\
    • c:\swtools\drivers\audio\vista\
    • c:\swsetup\sp73278\vista\
    • c:\swsetup\sp65606\vista\
    • c:\program files\realtek\installshield\
    • c:\dell\drivers\r274720\vista\
    • c:\swsetup\drv\audio\realtek\ppts1.xre_qqpxb2\6.0.1.8098\src\win32\
    • f:\program files\realtek\audio\hda\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_790c1ec79ba212da\
    • c:\windows\system32\driverstore\filerepository\hdasrsa.inf_x86_neutral_9dab712ac783ae14\
    • c:\swsetup\sp78707\win32\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_449ceaeeb59c8e0d\
    • c:\drivers\gigabyte mobo\audio\realtek\hd_audio\wdm\
    • c:\msi\liveupdate\dl_file\realtek_hd_audio_drivers_6.0.1.8105\win32\
    • c:\msi\liveupdate\dl_file\realtek_hd_audio_drivers_6.0.1.8412\win32\
    • c:\swsetup\drv\audio\realtek\gd1.xreal_ssrbb2\6.0.1.8397\src\win32\
    • c:\swsetup\sp80793\win32\
    • c:\swsetup\sp34734\wdm\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_neutral_b54a2636c8b1ce0a\
    • c:\windows\system32\driverstore\filerepository\hdartgi.inf_x86_neutral_d84429f0a09a290f\
    • c:\swsetup\sp82119\win32\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_02156840d3e39e27\
    • c:\program files\realtek\audio\drivers\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_42b380e2614ecab7\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_32c1cdaed76689dd\
    • c:\dell\drivers\r198875\vista\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_2e62b84f1fe92c56\
    • c:\drivers\realtek high definition audio driver\vista\
    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 rtlupd.exe file that is infected with malicious code:
    rtlupd.exe running statusTake up memory 390K
    Occupy CPU resources between 54% - 74%
    Run the program with the Administrator permissions.
    At runtime, 14 Windows system files, 0 external files (not owned by the Windows system), are called
    Windows system files
  • File name
  • Number of calling functions
  • SETUPAPI.dll
  • 21
  • newdev.dll
  • 1
  • VERSION.dll
  • 3
  • KERNEL32.dll
  • 146
  • USER32.dll
  • 123
  • GDI32.dll
  • 32
  • comdlg32.dll
  • 1
  • WINSPOOL.DRV
  • 3
  • ADVAPI32.dll
  • 15
  • SHELL32.dll
  • 1
  • SHLWAPI.dll
  • 5
  • oledlg.dll
  • 1
  • ole32.dll
  • 15
  • OLEAUT32.dll
  • 12
  • 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.
    rtlupd.exe 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. )
  • FlushFileBuffers: Flushes the buffers of a specified file and causes all buffered data to be written to a file.
  • DuplicateHandle: Duplicates an object handle.
  • SetErrorMode: Controls whether the system will handle the specified types of serious errors or whether the process will handle them.
  • GetTickCount: Retrieves the number of milliseconds that have elapsed since the system was started, up to 49.7 days.
  • GetStartupInfoW: Retrieves the contents of the STARTUPINFO structure that was specified when the calling process was created.
  • RtlUnwind: Initiates an unwind of procedure call frames.
  • ExitProcess: Ends the calling process and all its threads.
  • GetSystemInfo: Retrieves information about the current system.
  • SetUnhandledExceptionFilter: Enables an application to supersede the top-level exception handler of each thread of a process.
  • GetStdHandle: Retrieves a handle to the specified standard device (standard input, standard output, or standard error).
  • GetModuleFileNameA: Retrieves the fully qualified path for the file that contains the specified module.
  • FreeEnvironmentStringsA: Frees a block of environment strings.
  • FreeEnvironmentStringsW: Frees a block of environment strings.
  • GetEnvironmentStringsW: Retrieves the environment variables for the current process.
  • GetStartupInfoA: Retrieves the contents of the STARTUPINFO structure that was specified when the calling process was created.
  • 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.
  • GetSystemTimeAsFileTime: Retrieves the current system date and time. The information is in Coordinated Universal Time (UTC) format.
  • TerminateProcess: Ends the calling process and all its threads.
  • UnhandledExceptionFilter: An application-defined function that passes unhandled exceptions to the debugger, if the process is being debugged.
  • IsDebuggerPresent: Determines whether the calling process is being debugged by a user-mode debugger.
  • GetConsoleMode: Retrieves the current input mode of a console's input buffer or the current output mode of a console screen buffer.
  • WriteConsoleA: Writes a character string to a console screen buffer beginning at the current cursor location.
  • WriteConsoleW: Writes a character string to a console screen buffer beginning at the current cursor location.
  • SetEnvironmentVariableA: Sets the contents of the specified environment variable for the current process.
  • 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.
  • GetModuleHandleA: Retrieves a module handle for the specified module. The module must have been loaded by the calling process.
  • LoadLibraryA: Loads the specified module into the address space of the calling process. The specified module may cause other modules to be loaded.
  • GetCurrentProcessId: Retrieves the process identifier of the calling process.
  • GetCurrentThreadId: Retrieves the thread identifier of the calling thread.
  • InterlockedExchange: Sets a 32-bit variable to the specified value as an atomic operation.
  • CreateThread: Creates a thread to execute within the virtual address space of the calling process.
  • GetModuleFileNameW: Retrieves the fully qualified path for the file that contains the specified module.
  • WaitForSingleObject: Waits until the specified object is in the signaled state or the time-out interval elapses.
  • 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.
  • LoadLibraryW: Loads the specified module into the address space of the calling process. The specified module may cause other modules to be loaded.
  • GetProcAddress: Retrieves the address of an exported function or variable from the specified dynamic-link library (DLL).
  • GetLastError: Retrieves the calling thread's last-error code value.
  • The USER32.dll dynamic link library is loaded and the functions in the file are called: ( User32.dlll is a Windows user interface related application program interface for Windows processing, basic user interface and other features, such as creating windows and sending messages. )
  • GetWindowRect: Retrieves the dimensions of the bounding rectangle of the specified window.
  • 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\ )
  • RegQueryValueW: Retrieves the data associated with the default or unnamed value of a specified registry key.
  • RegQueryValueExW: Retrieves the data associated with the default or unnamed value of a specified registry key.
  • RegOpenKeyW: Opens the specified registry key. Note that key names are not case sensitive.
  • OpenProcessToken: This function opens the access token associated with a process.
  • LookupPrivilegeValueW: This function retrieves the locally unique identifier (LUID) used on a specified system to locally represent the specified privilege name.
  • AdjustTokenPrivileges: The AdjustTokenPrivileges function enables or disables privileges in the specified access token.
  • RegOpenKeyExW: Opens the specified registry key. Note that key names are not case sensitive.
  • The SHELL32.dll dynamic link library is loaded and the functions in the file are called: ( Shell32.dll is an important file stored in the \Windows\System32\ folder. Normally it is created automatically during the installation of the operating system and is critical to the normal operation of the system. Under normal circumstances, users are not advised to make arbitrary modifications to this type of file. Its existence plays an important role in maintaining the stability of the computer system. )
  • ShellExecuteW: Performs an operation on a specified file.
  • The following files have been identified as malicious files. Some files are variants of rtlupd.exe; some files are another type of malicious file, but use the same file name as rtlupd.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 rtlupd.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 rtlupd.exe is running, end this program.
    rtlupd.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 [  rtlupd.exe  ]

    • c:\dbz6675b\
    • c:\windows\system32\driverstore\filerepository\hdacr.inf_x86_d64f941046b33a97\
    • c:\drivers\audio\j4pj1\wdm\
    • c:\acer\empowering technology\erecovery\autorun\sw1\audio\wdm\
    • c:\windows\system32\driverstore\filerepository\hdart.inf_x86_neutral_a9dd3462d2552c4c\
    • c:\drivers\alc1200_audio_v6015859_windows7\vista\

    • 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 rtlupd.exe

    If you don't know if rtlupd.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:
    kb888111xpsp2.exe file analysis
    rtkaudioservice.exe file analysis
    rthdvbg.exe file analysis
    vncutil.exe file analysis
    skytel.exe file analysis
    alcmtr.exe file analysis
    delltouchpad.exe file analysis
    delltpad.exe file analysis
    removemysql-python.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.