GridinSoft Threat Intelligence

WinRARx86Eng.exe file report

Under review File reputation report
MD5 12688ce976701440ee524014e39895ce
Latest seen 2021-11-12 21:44:37 (4 years ago)
First seen 2017-10-27 23:06:52 (8 years ago)
Size 1 MB
Signed by win.rar GmbH

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-10-27 23:06:52 (8 years ago); latest analysis 2021-11-12 21:44:37 (4 years ago).

Digital signature

Signed by win.rar GmbH. 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.

WinRARx86Eng.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-11-12 21:44:37 (4 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: 12688ce976701440ee524014e39895ce
Size: 1 MB
First Published: 2017-10-27 23:06:52 (8 years ago)
Latest Published: 2021-11-12 21:44:37 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-12 21:44:37 (4 years ago)
Signed By: win.rar GmbH
Status: Valid

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

%appdata%\drpsu\programs
%sysdrive%\adwcleaner\quarantine\rywtiizs2t\programs
%appdata%\drpsu

ThreatInfo has observed WinRARx86Eng.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 73.3%
Windows 7 26.7%

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

WinRARx86Eng.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 0x0001c869
Image base 0x00400000

PE Sections:

Sections 6
Raw data 290304

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

.text 187392 bytes · 64.6% of section data
MD5 bd82d1e88b42da42e0738e302ad81934
.rdata 38912 bytes · 13.4% of section data
MD5 a11321ff400168a5ff29693ec6e6ddeb
.data 3072 bytes · 1.1% of section data
MD5 a91d0c766bd3fd878f0360d58f4f6110
.gfids 512 bytes · 0.2% of section data
Uncommon name
MD5 b5be945aaac5747977f70e4041c707b0
.rsrc 52224 bytes · 18.0% of section data
MD5 9ed35dd070d6dd55613248710365e70f
.reloc 8192 bytes · 2.8% of section data
MD5 6745cede4847a5415e6b62e7d792bd6d

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 12688ce976701440ee524014e39895ce.
  • 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.