GridinSoft Threat Intelligence

Logger.exe file report

Under review File reputation report
MD5 cb63910b25072527506bd8695e225886
Latest seen 2022-03-03 23:25:19 (4 years ago)
First seen 2018-02-08 18:06:52 (8 years ago)
Size 571 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-02-08 18:06:52 (8 years ago); latest analysis 2022-03-03 23:25:19 (4 years ago).

Digital signature

Signed by Reason Software Company Inc.. 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.

Logger.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-03-03 23:25:19 (4 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.

MD5: cb63910b25072527506bd8695e225886
Size: 571 KB
First Published: 2018-02-08 18:06:52 (8 years ago)
Latest Published: 2022-03-03 23:25:19 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-03-03 23:25:19 (4 years ago)
Signed By: Reason Software Company Inc.
Status: Valid

The signature on Logger.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 Logger.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 60.0%
Windows 8.1 20.0%
Windows 7 20.0%

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

Logger.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 0x00023e37
Image base 0x00400000

PE Sections:

Sections 7
Raw data 571392

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

.text 386560 bytes · 67.7% of section data
MD5 670433818100ab761b8c8b36ffe9b454
.rdata 138240 bytes · 24.2% of section data
MD5 1f5d607639c178a24b1bc9de7e05d1c3
.data 19968 bytes · 3.5% of section data
MD5 6eb59591b538826174d8aa6af74537c9
.gfids 3072 bytes · 0.5% of section data
Uncommon name
MD5 ae80dffbc70bd2d5d5d76c8bba2a01bc
.tls 512 bytes · 0.1% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 512 bytes · 0.1% of section data
MD5 f5eac9bb7a5931fe3c044829d9bd33dd
.reloc 22528 bytes · 3.9% of section data
MD5 09df73dc482b357e066984a2270304cc

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