GridinSoft Threat Intelligence

sdproxy.exe file report

Under review File reputation report
MD5 a321beaeee6b0d69056761cfcfc1c6d2
Latest seen 2021-02-03 04:30:38 (5 years ago)
First seen 2017-09-18 06:06:37 (8 years ago)
Size 91 KB
Publisher IObit

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-18 06:06:37 (8 years ago); latest analysis 2021-02-03 04:30:38 (5 years ago).

Publisher context

Company metadata: IObit.

Digital signature

Signed by IObit Information Technology. The signature is reported as valid, but signed files can still be bundled or abused.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

sdproxy.exe is a Windows file recorded in the ThreatInfo database. The reported company name is IObit. The current detection status is Undefined, based on the latest analysis from 2021-02-03 04:30:38 (5 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Company Name: IObit
MD5: a321beaeee6b0d69056761cfcfc1c6d2
Size: 91 KB
First Published: 2017-09-18 06:06:37 (8 years ago)
Latest Published: 2021-02-03 04:30:38 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-03 04:30:38 (5 years ago)
Signed By: IObit Information Technology
Status: Valid

The signature on sdproxy.exe 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.

%programfiles%\iobit\smart defrag
%programfiles%

ThreatInfo has observed sdproxy.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 7 100.0%

The most common operating system signal for sdproxy.exe is Windows 7 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.

sdproxy.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 0x00003f21
Image base 0x00400000

PE Sections:

Sections 5
Raw data 79360

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

.text 51712 bytes · 65.2% of section data
MD5 2181cb2e538b6eee4adf646058de5d69
.rdata 15360 bytes · 19.4% of section data
MD5 b28c12267ddf7975367bae901d41bf95
.data 4096 bytes · 5.2% of section data
MD5 7849c5fa91aacc0d2c04a560ccae3827
.rsrc 1536 bytes · 1.9% of section data
MD5 5d4f15eeb12e77eb08ec76cdcc5c2302
.reloc 6656 bytes · 8.4% of section data
MD5 7b629ab22a319a6841ab5de596f092e6

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 a321beaeee6b0d69056761cfcfc1c6d2.
  • 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.