GridinSoft Threat Intelligence

gemma.exe file report

Clean record File reputation report
MD5 66221b7145425d493ba8ff38a2fd3a5e
Latest seen 2021-03-30 20:06:17 (5 years ago)
First seen 2020-07-23 18:15:42 (5 years ago)
Size 1 MB
Signed by Bitdefender SRL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-07-23 18:15:42 (5 years ago); latest analysis 2021-03-30 20:06:17 (5 years ago).

Digital signature

Signed by Bitdefender SRL. 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.

gemma.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2021-03-30 20:06:17 (5 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.

MD5: 66221b7145425d493ba8ff38a2fd3a5e
Size: 1 MB
First Published: 2020-07-23 18:15:42 (5 years ago)
Latest Published: 2021-03-30 20:06:17 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-30 20:06:17 (5 years ago)
Signed By: Bitdefender SRL
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.

%programfiles%\bitdefender antivirus free\kitinstaller
%profile%\downloads\kitinstaller
%sysdrive%\$recycle.bin\s-1-5-21-2593625259-2115420800-3482615784-1001\$rq2iujw\kitinstaller

ThreatInfo has observed gemma.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 97.1%
Windows 7 2.9%

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

gemma.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 0x0001cab5
Image base 0x00400000

PE Sections:

Sections 6
Raw data 423424

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

.text 188416 bytes · 44.5% of section data
MD5 2ae181684b1677561119f5765623448e
.rdata 39424 bytes · 9.3% of section data
MD5 0e0f6a60d8fa917a060c8ef7becc0888
.data 3072 bytes · 0.7% of section data
MD5 4e4aa728d9cced1622c2be27733e3fc5
.gfids 512 bytes · 0.1% of section data
Uncommon name
MD5 c923099e27bf0e45a5c402d935d0620b
.rsrc 183808 bytes · 43.4% of section data
MD5 5b2ccaf393e2357bf79c122a0532b826
.reloc 8192 bytes · 1.9% of section data
MD5 d13d3f8a8adfe6861c49a01d81cf73ed

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 66221b7145425d493ba8ff38a2fd3a5e.
  • 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.