GridinSoft Threat Intelligence

InstAct.exe file report

Under review File reputation report
MD5 f60e6129f325dce6ab502831f5f05489
Latest seen 2024-10-15 23:06:54 (2 years ago)
First seen 2024-09-27 23:04:39 (2 years ago)
Size 33 KB
Publisher RealDefense LLC
Product MyCleanPC
Signed by RealDefense LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-09-27 23:04:39 (2 years ago); latest analysis 2024-10-15 23:06:54 (2 years ago).

Publisher context

Company metadata: RealDefense LLC. Product metadata: MyCleanPC.

Digital signature

Signed by RealDefense LLC. 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.

InstAct.exe is a Windows file recorded in the ThreatInfo database. It is associated with MyCleanPC. The reported company name is RealDefense LLC. The current detection status is Undefined, based on the latest analysis from 2024-10-15 23:06:54 (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.

Product Name: MyCleanPC
Company Name: RealDefense LLC
MD5: f60e6129f325dce6ab502831f5f05489
Size: 33 KB
First Published: 2024-09-27 23:04:39 (2 years ago)
Latest Published: 2024-10-15 23:06:54 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-10-15 23:06:54 (2 years ago)
Signed By: RealDefense LLC
Status: Valid

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

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

InstAct.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 0x00006766
Image base 0x00400000

.NET Info:

MVID: ea19faf5-4fa1-42d0-bee2-b838f5332c1a
Typelib ID: 656d6049-7987-4b5d-8ba8-3d076ca8b428

PE Sections:

Sections 3
Raw data 23040

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

.text 18432 bytes · 80.0% of section data
MD5 6d4c9003a12394c28a8a0dbfba980181
.reloc 512 bytes · 2.2% of section data
MD5 cbdfd98a90f803a1274387d3bec34d1d
.rsrc 4096 bytes · 17.8% of section data
MD5 e8c46679dae407ca9a645ccc0326504a

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