GridinSoft Threat Intelligence

GoogleUpdateBroker.exe file report

Under review File reputation report
MD5 70fdb50fd503e2e58c2ccf9d7e8a0d00
Latest seen 2022-08-03 23:29:00 (3 years ago)
First seen 2019-04-09 16:01:38 (7 years ago)
Size 96 KB
Publisher Bergarius LLC
Product Orbitum Update
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:01:38 (7 years ago); latest analysis 2022-08-03 23:29:00 (3 years ago).

Publisher context

Company metadata: Bergarius LLC. Product metadata: Orbitum Update.

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.

GoogleUpdateBroker.exe is a Windows file recorded in the ThreatInfo database. It is associated with Orbitum Update. The reported company name is Bergarius LLC. The current detection status is Undefined, based on the latest analysis from 2022-08-03 23:29:00 (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.

Product Name: Orbitum Update
Company Name: Bergarius LLC
MD5: 70fdb50fd503e2e58c2ccf9d7e8a0d00
Size: 96 KB
First Published: 2019-04-09 16:01:38 (7 years ago)
Latest Published: 2022-08-03 23:29:00 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-08-03 23:29:00 (3 years ago)
Signed By: Bergarius Limited
Status: Valid

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

GoogleUpdateBroker.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 0x00001716
Image base 0x00400000

PE Sections:

Sections 6
Raw data 86528

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

.text 44544 bytes · 51.5% of section data
MD5 afbcd31f6e898038770a984f50b5a909
.rdata 23040 bytes · 26.6% of section data
MD5 e944006588e465d772e388f4e22c11d6
.data 2048 bytes · 2.4% of section data
MD5 1cc1b55616ace5622031b546e7bfff23
.gfids 512 bytes · 0.6% of section data
Uncommon name
MD5 6647d93ee2709ebca864b068333db9f0
.rsrc 12800 bytes · 14.8% of section data
MD5 98abf289ba90409ead4e4680a14728b1
.reloc 3584 bytes · 4.1% of section data
MD5 7ed320ed5dcd91863757bd38ecef2f52

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 70fdb50fd503e2e58c2ccf9d7e8a0d00.
  • 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.