GridinSoft Threat Intelligence

GoogleUpdateComRegisterShell64.exe file report

Under review File reputation report
MD5 84c511237c0626238cff311111215d0c
Latest seen 2022-08-03 23:29:58 (3 years ago)
First seen 2019-04-09 16:04:01 (7 years ago)
Size 173 KB
Signed by Bergarius Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-04-09 16:04:01 (7 years ago); latest analysis 2022-08-03 23:29:58 (3 years ago).

Digital signature

Signed by Bergarius Limited. 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.

GoogleUpdateComRegisterShell64.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-08-03 23:29:58 (3 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: 84c511237c0626238cff311111215d0c
Size: 173 KB
First Published: 2019-04-09 16:04:01 (7 years ago)
Latest Published: 2022-08-03 23:29:58 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-03 23:29:58 (3 years ago)
Signed By: Bergarius Limited
Status: Valid

The signature on GoogleUpdateComRegisterShell64.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.

%localappdata%\orbitum\update

ThreatInfo has observed GoogleUpdateComRegisterShell64.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 62.5%
Windows 7 29.2%
Windows 8.1 8.3%

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

GoogleUpdateComRegisterShell64.exe is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00005e10
Image base 0x0000000140000000

PE Sections:

Sections 7
Raw data 165888

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

.text 84480 bytes · 50.9% of section data
MD5 b7c347699c9c047f1b9954163331cae9
.rdata 68096 bytes · 41.0% of section data
MD5 e3b63ade11eec77775a066b5e4e60a83
.data 3584 bytes · 2.2% of section data
MD5 f62e03b6c3e7822295beeed269947d77
.pdata 5632 bytes · 3.4% of section data
MD5 8d0c440efdbf18fad098bb7a2cdc7217
.gfids 512 bytes · 0.3% of section data
Uncommon name
MD5 577d16e369bb31ece1a9a8c09e4a6fd2
.tls 512 bytes · 0.3% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.reloc 3072 bytes · 1.9% of section data
MD5 63aa1a5c8b599c4688b21834dd569cd5

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 84c511237c0626238cff311111215d0c.
  • 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.