GridinSoft Threat Intelligence

googlemarathiinputsetup.exe file report

Clean record File reputation report
MD5 c33b7f9cf06ad8917c83c5ce29372934
Latest seen 2021-01-03 06:42:31 (5 years ago)
First seen 2021-01-03 06:42:31 (5 years ago)
Size 592 KB
Publisher Google Inc.
Product Google Update
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-01-03 06:42:31 (5 years ago); latest analysis 2021-01-03 06:42:31 (5 years ago).

Publisher context

Company metadata: Google Inc.. Product metadata: Google Update.

Digital signature

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

googlemarathiinputsetup.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google Update. The reported company name is Google Inc.. The current detection status is Clean, based on the latest analysis from 2021-01-03 06:42:31 (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.

Product Name: Google Update
Company Name: Google Inc.
MD5: c33b7f9cf06ad8917c83c5ce29372934
Size: 592 KB
First Published: 2021-01-03 06:42:31 (5 years ago)
Latest Published: 2021-01-03 06:42:31 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-03 06:42:31 (5 years ago)
Signed By: Google 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.

%desktop%\imp files & software

ThreatInfo has observed googlemarathiinputsetup.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 7 100.0%

The most common operating system signal for googlemarathiinputsetup.exe is Windows 7 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.

googlemarathiinputsetup.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 0x00004ea1
Image base 0x00400000

PE Sections:

Sections 5
Raw data 600576

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

.text 20480 bytes · 3.4% of section data
MD5 9211c97d50cb560ad9ea37b6710b6110
.rdata 4608 bytes · 0.8% of section data
MD5 1537ef936f8c99110f805a71d9c55a6e
.data 1024 bytes · 0.2% of section data
MD5 bc14a666df0c6e89d98cd93438636525
.rsrc 571904 bytes · 95.2% of section data
MD5 2a0bd6947b01d4b6b5039eeab57dff19
.reloc 2560 bytes · 0.4% of section data
MD5 fdb5d4271bccc95b7d7630c69640a2d0

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