GridinSoft Threat Intelligence

unrar.dll file report

Under review File reputation report
MD5 577c8f3cae2e8de5382e4e933f406765
Latest seen 2024-03-22 23:01:08 (2 years ago)
First seen 2017-05-26 14:07:40 (9 years ago)
Size 170 KB
Publisher Alexander Roshal
Product RAR decompression library
Signed by Beijing Baofeng Technology Co., Ltd.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-26 14:07:40 (9 years ago); latest analysis 2024-03-22 23:01:08 (2 years ago).

Publisher context

Company metadata: Alexander Roshal. Product metadata: RAR decompression library.

Digital signature

Signed by Beijing Baofeng Technology Co., 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. 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.

File context

unrar.dll is a Windows file recorded in the ThreatInfo database. It is associated with RAR decompression library. The reported company name is Alexander Roshal. The current detection status is Undefined, based on the latest analysis from 2024-03-22 23:01:08 (2 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.

File Details

Product Name: RAR decompression library
Company Name: Alexander Roshal
MD5: 577c8f3cae2e8de5382e4e933f406765
Size: 170 KB
First Published: 2017-05-26 14:07:40 (9 years ago)
Latest Published: 2024-03-22 23:01:08 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-03-22 23:01:08 (2 years ago)

Overview

Signed By: Beijing Baofeng Technology Co., Ltd.
Status: Valid

The signature on unrar.dll 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:

%programfiles%\baofeng\stormplayer
%sysdrive%\windows
%programfiles%\baofeng
%programfiles%
%commonappdata%\baofeng\stormplayer\update\stormplayerunzippackage

ThreatInfo has observed unrar.dll 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 unrar.dll across 14 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country China
Share 48.3%
Low High activity

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

OS Version:

Windows 10 72.5%
Windows 7 16.7%
Windows 8.1 5.0%
Windows XP 4.2%
Windows Server 2003 0.8%
Windows Server 2008 R2 0.8%

The most common operating system signal for unrar.dll is Windows 10 with 72.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.

Analysis

unrar.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x00001000
Image base 0x00400000

PE Sections:

Sections 7
Raw data 166912

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

.text 141312 bytes · 84.7% of section data
MD5 6984f3e856591720a5f54915b73f5fb8
.data 16384 bytes · 9.8% of section data
MD5 13e33e9bba9b76113d597ed995037403
.tls 512 bytes · 0.3% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.idata 2560 bytes · 1.5% of section data
MD5 af173ef1bd2b326d9c95f936ceb1e032
.edata 512 bytes · 0.3% of section data
MD5 de2a0e2d265b42700b77be7b29606630
.rsrc 1024 bytes · 0.6% of section data
MD5 481ca5d4f23dd52e6fdf7f9aeea01e43
.reloc 4608 bytes · 2.8% of section data
MD5 6b739b899531e3398eb45d08a31a8fee

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 577c8f3cae2e8de5382e4e933f406765.
  • 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.