GridinSoft Threat Intelligence

bTagRestore.exe file report

Under review File reputation report
MD5 be513df55ce3659999ee975ac341a95a
Latest seen 2021-01-05 13:43:10 (5 years ago)
First seen 2021-01-03 05:26:23 (5 years ago)
Size 5 MB
Signed by Softland SRL

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-03 05:26:23 (5 years ago); latest analysis 2021-01-05 13:43:10 (5 years ago).

Digital signature

Signed by Softland SRL. 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.

bTagRestore.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-01-05 13:43:10 (5 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: be513df55ce3659999ee975ac341a95a
Size: 5 MB
First Published: 2021-01-03 05:26:23 (5 years ago)
Latest Published: 2021-01-05 13:43:10 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-05 13:43:10 (5 years ago)
Signed By: Softland SRL
Status: Valid

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

%programfiles%
%programfiles%\softland

ThreatInfo has observed bTagRestore.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 100.0%

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

bTagRestore.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 0x010c8000
Image base 0x00400000

PE Sections:

Sections 6
Raw data 5278208

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

2554880 bytes · 48.4% of section data
Uncommon name
MD5 ba150d8e0382c240fb70a6ff62b80d25
.rsrc 162304 bytes · 3.1% of section data
MD5 4e3c6283f86ea105590e2f37f74ea3c5
.idata 512 bytes · 0.0% of section data
Uncommon name
MD5 61eab419cf74987956c9e59d1f0d1740
512 bytes · 0.0% of section data
Uncommon name
MD5 30e041956710d38594cf000da07cd2a0
edpydmfz 2559488 bytes · 48.5% of section data
Uncommon name
MD5 b880f97a1ebc9679e9266954182aa652
ynmjclnv 512 bytes · 0.0% of section data
Uncommon name
MD5 e1f5e3b840c1aec61f2b42e378f140a8

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 be513df55ce3659999ee975ac341a95a.
  • 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.