zamzar.exe threat report

MD5 45a07bf011a686ae71f7c54e35e7eac6
Latest seen 2024-04-27 23:01:57 (2 years ago)
First seen 2024-04-27 23:01:57 (2 years ago)
Size 155 MB
Publisher Zamzar
Product Zamzar
Signed by Zamzar Ltd

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Possible Threat. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Possible Threat
Recommended action
Scan and remove
Last analysis
2024-04-27 23:01:57 (2 years ago)
File hash
45a07bf011a686ae71f7c54e35e7eac6
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Possible Threat.

Timeline

First seen 2024-04-27 23:01:57 (2 years ago); latest analysis 2024-04-27 23:01:57 (2 years ago).

Publisher context

Company metadata: Zamzar. Product metadata: Zamzar.

Digital signature

Signed by Zamzar Ltd. 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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

zamzar.exe is a Windows file recorded in the ThreatInfo database. It is associated with Zamzar. The reported company name is Zamzar. The current detection status is Possible Threat, based on the latest analysis from 2024-04-27 23:01:57 (2 years ago).

If zamzar.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Possible Threat.

Product Name: Zamzar
Company Name: Zamzar
MD5: 45a07bf011a686ae71f7c54e35e7eac6
Size: 155 MB
First Published: 2024-04-27 23:01:57 (2 years ago)
Latest Published: 2024-04-27 23:01:57 (2 years ago)
Status: Possible Threat (on last analysis)
Analysis Date: 2024-04-27 23:01:57 (2 years ago)
zamzar.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: Zamzar Ltd
Status: Valid

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

ThreatInfo has observed zamzar.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.

100.0%

The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for zamzar.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.

zamzar.exe is identified as pe for 64 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x04243450

PE Sections:

Name Size of data MD5
.text 133338112 60e838ec3043e52607fb8c1d17ece35f
.rdata 24025600 09dfcbc24f1db1ba3c272ec8b08777fd
.data 522752 7e203ca4afecae0b09aae0db5a2be557
.pdata 4268032 4edba9b06638028bf1fcd2f48928d6eb
.00cfg 512 fb81a9d024a61cce4195c2dc18535db1
.gxfg 16896 d3843f732ebd476abf4c084b5dfd8895
.retplne 512 d51aa2afe8c4966881241a9482b95b51
.rodata 4608 c642bc1527b5873b6dbf56c4a87d20cb
.tls 1536 79f08bb96c6470ca7bef9a70adde268d
CPADinfo 512 60d3ea61d541c9be2e845d2787fb9574
LZMADEC 4608 05e9eab8428a551a281ab278073669fa
_RDATA 512 48fe9011f47355cd8fa4ea2fae5145e3
malloc_h 512 fca0e74c04153436abb68dfde94df1d9
.rsrc 90624 feddc155da67c0cf5763a255914af136
.reloc 936960 a52217a879dae4b7fd77366cf50d5995

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.

More information: