GridinSoft Threat Intelligence
winusbcoinstaller2.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-05-22 10:26:31 (8 years ago); latest analysis 2023-06-07 23:02:30 (2 years ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Windows® Operating System.
Signed by Microsoft Windows Component Publisher. The signature is reported as valid, but signed files can still be bundled or abused.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
winusbcoinstaller2.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Windows® Operating System. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2023-06-07 23:02:30 (2 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Microsoft® Windows® Operating System |
| Company Name: | Microsoft Corporation |
| MD5: | 246900ce6474718730ecd4f873234cf5 |
| Size: | 979 KB |
| First Published: | 2017-05-22 10:26:31 (8 years ago) |
| Latest Published: | 2023-06-07 23:02:30 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2023-06-07 23:02:30 (2 years ago) |
Overview
| Signed By: | Microsoft Windows Component Publisher |
| Status: | Valid |
The signature on winusbcoinstaller2.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %appdata%\mobogenie\driver\driverfolder\androidcommon_64\amd64 |
| %programfiles%\wiselinktool\drivers\sp_drivers_exe_v1.6\amd64 |
| %programfiles%\wiselinktool\drivers\adb_usb_driver_v2.0\amd64 |
| %programfiles%\wiselinktool\drivers\driver_auto_installer_exe_v1.1352.00\smartphonedriver\x64\unsigned infs\amd64 |
| %programfiles%\tabletdriver\driver\tabletdriver\amd64 |
| %appdata%\tencent\androidserver\deviceinfo\drivers\d_base_64_v4\amd64 |
| %temp%\xunlei\xldevicemanager\5546278ddriverdir\amd64 |
| %temp%\xunlei\xldevicemanager\554623ecdriverdir\amd64 |
| %temp%\xunlei\xldevicemanager\5546264adriverdir\amd64 |
| %temp%\xunlei\xldevicemanager\5546273cdriverdir\amd64 |
ThreatInfo has observed winusbcoinstaller2.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen winusbcoinstaller2.dll across 83 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 13.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for winusbcoinstaller2.dll is Windows 7 with 54.1% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
winusbcoinstaller2.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
ef294ac2b60a4b80f5bca57a425fa11e
9460c6b0bc607cd250612fb6a475f326
57e0c64b8996bab978dc85d24aee11eb
f0da1d5a397f447e0241a9daed289fa4
a1f9292200b6776380e541dd07248c4d
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.