GridinSoft Threat Intelligence

FixComponents.exe file report

Under review File reputation report
MD5 c76f0f1d6802be5f39398f30fec26c12
Latest seen 2021-02-09 04:41:49 (5 years ago)
First seen 2020-03-31 23:46:35 (6 years ago)
Size 5 MB
Publisher Soft4Boost Ltd
Product FixComponents 3.4
Signed by Kahan Michael

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2020-03-31 23:46:35 (6 years ago); latest analysis 2021-02-09 04:41:49 (5 years ago).

Publisher context

Company metadata: Soft4Boost Ltd. Product metadata: FixComponents 3.4.

Digital signature

Signed by Kahan Michael. 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

FixComponents.exe is a Windows file recorded in the ThreatInfo database. It is associated with FixComponents 3.4. The reported company name is Soft4Boost Ltd. The current detection status is Undefined, based on the latest analysis from 2021-02-09 04:41:49 (5 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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: FixComponents 3.4
Company Name: Soft4Boost Ltd
MD5: c76f0f1d6802be5f39398f30fec26c12
Size: 5 MB
First Published: 2020-03-31 23:46:35 (6 years ago)
Latest Published: 2021-02-09 04:41:49 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-09 04:41:49 (5 years ago)

Overview

Signed By: Kahan Michael
Status: Valid

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

%commondir%

ThreatInfo has observed FixComponents.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 FixComponents.exe across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Russian Federation
Share 66.7%
Low High activity

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

OS Version:

Windows 7 66.7%
Windows 10 33.3%

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

FixComponents.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 0x000017d0
Image base 0x00400000

PE Sections:

Sections 8
Raw data 5390848

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

.text 2502144 bytes · 46.4% of section data
MD5 22a7a5b817ef3e9e9165ae9fe4d353f4
.data 151040 bytes · 2.8% of section data
MD5 0109ca5d369fd4d26a52a83c13a4b710
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rdata 512 bytes · 0.0% of section data
MD5 3852e071a80d16e3b939cd133ff533d0
.idata 14848 bytes · 0.3% of section data
MD5 5af2ec1c1da02ab3e2806ca52cfd432c
.edata 454656 bytes · 8.4% of section data
MD5 3ecea4d7e0281d1335bf1d54bb620bfe
.rsrc 2126848 bytes · 39.5% of section data
MD5 3e61bb04541b75cb2de4186a46dfd692
.reloc 140288 bytes · 2.6% of section data
MD5 37fc9773f494d4b8d567b78c43cc1a1c

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 c76f0f1d6802be5f39398f30fec26c12.
  • 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. Use the PUP category to compare similar reports.