GridinSoft Threat Intelligence

GOM.EXE file report

Under review File reputation report
MD5 852c27cee34205c1cd07a72617ddb9c6
Latest seen 2021-02-04 16:24:59 (5 years ago)
First seen 2020-09-11 22:53:20 (5 years ago)
Size 8 MB
Product GOM Player
Signed by GRETECH

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-09-11 22:53:20 (5 years ago); latest analysis 2021-02-04 16:24:59 (5 years ago).

Publisher context

Product metadata: GOM Player.

Digital signature

Signed by GRETECH. 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.

GOM.EXE is a Windows file recorded in the ThreatInfo database. It is associated with GOM Player. The current detection status is Undefined, based on the latest analysis from 2021-02-04 16:24:59 (5 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: GOM Player
MD5: 852c27cee34205c1cd07a72617ddb9c6
Size: 8 MB
First Published: 2020-09-11 22:53:20 (5 years ago)
Latest Published: 2021-02-04 16:24:59 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-04 16:24:59 (5 years ago)
Signed By: GRETECH
Status: Valid

The signature on GOM.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%\gretech

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

40.0%
36.0%
16.0%
4.0%
4.0%

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

Windows 7 56.0%
Windows 10 40.0%
Windows XP 4.0%

The most common operating system signal for GOM.EXE is Windows 7 with 56.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.

GOM.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 0x003eef1d
Image base 0x00400000

PE Sections:

Sections 6
Raw data 8420352

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

.text 4685824 bytes · 55.6% of section data
MD5 6253a35b5e0ee739ed83102f0016ea32
.rdata 1269248 bytes · 15.1% of section data
MD5 80b737c00ef870aa4c8e803b6861ef3c
.data 132608 bytes · 1.6% of section data
MD5 8b5bd08f572ddda23260058871ec15cd
.GOMSH 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1977344 bytes · 23.5% of section data
MD5 75f0a05e3c6f5ad1aacc66d6ff97b96f
.reloc 354816 bytes · 4.2% of section data
MD5 8851e959884d169da6ec6e5734a27492

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 852c27cee34205c1cd07a72617ddb9c6.
  • 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.