GridinSoft Threat Intelligence

installer.exe file report

Clean record File reputation report
MD5 e48fbbd1fe627aa30e931ddddf621a77
Latest seen 2023-06-02 23:52:36 (2 years ago)
First seen 2023-04-02 23:02:14 (3 years ago)
Size 65 MB
Publisher Trend Micro, Inc.
Product Cleaner One Pro
Signed by Trend Micro, Inc.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-04-02 23:02:14 (3 years ago); latest analysis 2023-06-02 23:52:36 (2 years ago).

Publisher context

Company metadata: Trend Micro, Inc.. Product metadata: Cleaner One Pro.

Digital signature

Signed by Trend Micro, 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.

installer.exe is a Windows file recorded in the ThreatInfo database. It is associated with Cleaner One Pro. The reported company name is Trend Micro, Inc.. The current detection status is Clean, based on the latest analysis from 2023-06-02 23:52:36 (2 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.

Product Name: Cleaner One Pro
Company Name: Trend Micro, Inc.
MD5: e48fbbd1fe627aa30e931ddddf621a77
Size: 65 MB
First Published: 2023-04-02 23:02:14 (3 years ago)
Latest Published: 2023-06-02 23:52:36 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-06-02 23:52:36 (2 years ago)
Signed By: Trend Micro, 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.

%localappdata%

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

installer.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 0x0000338f
Image base 0x00400000

PE Sections:

Sections 5
Raw data 324608

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

.text 26624 bytes · 8.2% of section data
MD5 7618d4c0cd8bb67ea9595b4266b3a91f
.rdata 5632 bytes · 1.7% of section data
MD5 eecac1fed9cc6b447d50940d178404d8
.data 1536 bytes · 0.5% of section data
MD5 db8f31a08a2242d80c29e1f9500c6527
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.rsrc 290816 bytes · 89.6% of section data
MD5 1569264e73238b4e94a9894422b80d7a

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