GridinSoft Threat Intelligence

ICONPIN64.exe file report

Under review File reputation report
MD5 4811809a0b69533e16ebea18863df282
Latest seen 2023-10-14 23:02:56 (2 years ago)
First seen 2021-02-03 16:38:01 (5 years ago)
Size 571 KB
Publisher IObit
Product IObit Common Component
Signed by IObit Information Technology

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-02-03 16:38:01 (5 years ago); latest analysis 2023-10-14 23:02:56 (2 years ago).

Publisher context

Company metadata: IObit. Product metadata: IObit Common Component.

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.

File context

ICONPIN64.exe is a Windows file recorded in the ThreatInfo database. It is associated with IObit Common Component. The reported company name is IObit. The current detection status is Undefined, based on the latest analysis from 2023-10-14 23:02:56 (2 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.

File Details

Product Name: IObit Common Component
Company Name: IObit
MD5: 4811809a0b69533e16ebea18863df282
Size: 571 KB
First Published: 2021-02-03 16:38:01 (5 years ago)
Latest Published: 2023-10-14 23:02:56 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-10-14 23:02:56 (2 years ago)

Overview

Signed By: IObit Information Technology
Status: Valid

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

Common Places:

%programfiles%\iobit\driver booster\8.1.0
%programfiles%\iobit\driver booster\8.2.0
%programfiles%\iobit\driver booster\8.3.0
%programfiles%\steam\steamapps\common\driver booster for steam
%programfiles%\driverbooster

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

Geographic signal

Observed country distribution

ThreatInfo has seen ICONPIN64.exe across 11 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 21.4%
Low High activity

The strongest geographic signal for this file is United States with 21.4% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 78.6%
Windows 7 21.4%

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

ICONPIN64.exe is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x000737e0
Image base 0x0000000000400000

PE Sections:

Sections 9
Raw data 571392

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

.text 475648 bytes · 83.2% of section data
MD5 727fdc498e14e3d9f3063d86caedd416
.data 52224 bytes · 9.1% of section data
MD5 10c392dce53aa997d25684a7466b53e4
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 5632 bytes · 1.0% of section data
MD5 cd7e160716d6fd2b7bfbabba8f92adb1
.didata 512 bytes · 0.1% of section data
Uncommon name
MD5 ce23187eefe79781b91723fc69265732
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.1% of section data
MD5 7bcbd48ce98b1c9c0ff2905d83eceee7
.pdata 27136 bytes · 4.7% of section data
MD5 f7e7bb6a7077af6d16c86aba932fa0d3
.rsrc 9728 bytes · 1.7% of section data
MD5 2783b73a737a3d127fe6ae0e14c63243

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 4811809a0b69533e16ebea18863df282.
  • 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.