GridinSoft Threat Intelligence

GPlus_UFRII_Driver_V250_W64_00.exe file report

Clean record File reputation report
MD5 6b7ec5ea6aad64004c92f7d7d34169bd
Latest seen 2021-12-16 21:54:19 (4 years ago)
First seen 2021-12-16 21:53:01 (4 years ago)
Size 32 MB
Signed by CANON INC.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-12-16 21:53:01 (4 years ago); latest analysis 2021-12-16 21:54:19 (4 years ago).

Digital signature

Signed by CANON INC.. ThreatInfo marks this publisher as trusted for this record.

Observed locations

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

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

GPlus_UFRII_Driver_V250_W64_00.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-12-16 21:54:19 (4 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.

MD5: 6b7ec5ea6aad64004c92f7d7d34169bd
Size: 32 MB
First Published: 2021-12-16 21:53:01 (4 years ago)
Latest Published: 2021-12-16 21:54:19 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-16 21:54:19 (4 years ago)
Signed By: CANON INC.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%desktop%
%sysdrive%\downloads
%sysdrive%

ThreatInfo has observed GPlus_UFRII_Driver_V250_W64_00.exe 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.

Windows 10 100.0%

The most common operating system signal for GPlus_UFRII_Driver_V250_W64_00.exe is Windows 10 with 100.0% 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.

GPlus_UFRII_Driver_V250_W64_00.exe is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00014bdf
Image base 0x00400000

PE Sections:

Sections 5
Raw data 34197504

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 151552 bytes · 0.4% of section data
MD5 e5e08c1bf29516f79f30afda604f6d4b
.rdata 28672 bytes · 0.1% of section data
MD5 e044f73f7cc069a25cfb1ede062ed59a
.data 8192 bytes · 0.0% of section data
MD5 757e83b9c3ae360ea456d9de2b899a50
.rsrc 40960 bytes · 0.1% of section data
MD5 cef93ff46f03e40ae80e748bd8f76457
_winzip_ 33968128 bytes · 99.3% of section data
Large raw data Uncommon name
MD5 962009fe4534675dd95fa0c440970bc9

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.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 6b7ec5ea6aad64004c92f7d7d34169bd.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.