Dezor.exe threat report

MD5 adb9b68182175112ad07b97468743d61
Latest seen 2023-04-11 23:32:35 (3 years ago)
First seen 2023-04-11 23:32:35 (3 years ago)
Size 147 MB
Publisher GitHub, Inc.
Product Dezor
Signed by Dezor SA

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2023-04-11 23:32:35 (3 years ago)
File hash
adb9b68182175112ad07b97468743d61
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2023-04-11 23:32:35 (3 years ago); latest analysis 2023-04-11 23:32:35 (3 years ago).

Publisher context

Company metadata: GitHub, Inc.. Product metadata: Dezor.

Digital signature

Signed by Dezor SA. 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.

Dezor.exe is a Windows file recorded in the ThreatInfo database. It is associated with Dezor. The reported company name is GitHub, Inc.. The current detection status is Trojan.Heur!, based on the latest analysis from 2023-04-11 23:32:35 (3 years ago).

If Dezor.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 Trojan.Heur!.

Product Name: Dezor
Company Name: GitHub, Inc.
MD5: adb9b68182175112ad07b97468743d61
Size: 147 MB
First Published: 2023-04-11 23:32:35 (3 years ago)
Latest Published: 2023-04-11 23:32:35 (3 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2023-04-11 23:32:35 (3 years ago)
Dezor.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: Dezor SA
Status: Valid

The signature on Dezor.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%\programs

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

Dezor.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: 0x03def2d0

PE Sections:

Name Size of data MD5
.text 124934144 aa30111aac4fa0b275d1b75a5230f8ee
.rdata 23342592 bd4a17be60d0a7a876373a47863b9c34
.data 737792 f17ec827dfe6418118c513976ec8fcd4
.pdata 4001280 50fc2ccf226977f145158f3d6d69509e
.00cfg 512 dde2ae8aa8b7c8d262760e09fb71b814
.gxfg 16896 de20bccbaa57d2a92479293db53dcf85
.retplne 512 d71c80853fa92a73d6e7b213fb3fe5de
.rodata 4608 e5c4f94e5f0f18c0a0c02e29f559138d
.tls 1024 3540e4fa9ead49b55e3604a8b9ec6d37
.voltbl 512 a3c251baa31d5e55e2ec45f9019f79e1
CPADinfo 512 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 e3fbddfb0d7e71c080377cb07b273f00
malloc_h 512 f7d30c44541764fe5dace0c18fe38243
.rsrc 106496 878d2312a1872243afcec31ded3e5478
.reloc 990208 de98189972c171610e1b22a6fb5cc7fb

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: