GridinSoft Threat Intelligence
UpdateMessenger.exe file report
Why it matters
Evidence available for this file
No final classification is available yet.
Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.
First seen 2020-06-05 16:29:19 (5 years ago); latest analysis 2021-03-20 21:05:55 (5 years ago).
Company metadata: SweetLabs, Inc. Product metadata: Update Messenger.
Signed by SweetLabs Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
UpdateMessenger.exe is a Windows file recorded in the ThreatInfo database. It is associated with Update Messenger. The reported company name is SweetLabs, Inc. The current detection status is Undefined, based on the latest analysis from 2021-03-20 21:05:55 (5 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.
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.
File Details
| Product Name: | Update Messenger |
| Company Name: | SweetLabs, Inc |
| MD5: | d7cb7fd593da53860214154efa44e05d |
| Size: | 13 MB |
| First Published: | 2020-06-05 16:29:19 (5 years ago) |
| Latest Published: | 2021-03-20 21:05:55 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-03-20 21:05:55 (5 years ago) |
Overview
| Signed By: | SweetLabs Inc. |
| Status: | Valid |
The signature on UpdateMessenger.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.
Common Places:
| %localappdata% |
| %temp% |
ThreatInfo has observed UpdateMessenger.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.
Geographic signal
Observed country distribution
ThreatInfo has seen UpdateMessenger.exe across 14 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 16.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for UpdateMessenger.exe is Windows 10 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.
Analysis
UpdateMessenger.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
37f8889ee10c6be0b4b44901c8bfcf4e
7013d9049b78e3d2e8ea3ca78d6a9e33
9de3636b6ffce21b3e704c64e3a6a4ef
e96da0e4df092856f7040d54c68e33b0
bde2384039c08660f75d109b21db6a03
e291769b656fe44d57ceaf6015073211
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.