bRestore.exe file report

MD5 12eb3cc5c6a11c7ccb772e67bcf2eb77
Latest seen 2021-12-05 21:24:34 (4 years ago)
First seen 2021-12-05 21:24:34 (4 years ago)
Size 9 MB
Publisher Softland
Product Backup4all
Signed by Softland SRL

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-12-05 21:24:34 (4 years ago); latest analysis 2021-12-05 21:24:34 (4 years ago).

Publisher context

Company metadata: Softland. Product metadata: Backup4all.

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.

bRestore.exe is a Windows file recorded in the ThreatInfo database. It is associated with Backup4all. The reported company name is Softland. The current detection status is Undefined, based on the latest analysis from 2021-12-05 21:24:34 (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.

Product Name: Backup4all
Company Name: Softland
MD5: 12eb3cc5c6a11c7ccb772e67bcf2eb77
Size: 9 MB
First Published: 2021-12-05 21:24:34 (4 years ago)
Latest Published: 2021-12-05 21:24:34 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-12-05 21:24:34 (4 years ago)
Signed By: Softland SRL
Status: Valid

The signature on bRestore.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%\softland

ThreatInfo has observed bRestore.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 Czech Republic 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 bRestore.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.

bRestore.exe is identified as pe for 32 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: 32
Image Base: 0x00400000
Entry Address: 0x01849058

PE Sections:

Name Size of data MD5
3854848 5286b176a8777b2323c5f113bc1f5e73
15872 1d2e5ec04914344748131c2e353dfc8d
269824 3be38b9f664222b7a7049fddb4e9c5c8
.bss 0 d41d8cd98f00b204e9800998ecf8427e
3584 3b8be4cf3f272558df146116cf38a56a
1536 321cf10c28f4f97195798f9f350441e7
512 dde963337e91684205ebd67f71a3aef5
.tls 0 d41d8cd98f00b204e9800998ecf8427e
512 a8833743ea4b9387fb4d866db1a944d8
423936 87ea00293ff3cb7d52a0c81f0a7e86c4
204288 6bf5e6eb0e747cb63c8546510b3bdb27
.edata 512 ba64ff370f1ef0648c1b0fe71dc66f05
.idata 2048 3e5dcb36b0060d449993cc225b5883cb
.tls 2048 6b0548022885b309c5dfcd9dedce75f9
.rsrc 50688 6d973976d26183d89e1be2ac6e96e59d
.themida 0 d41d8cd98f00b204e9800998ecf8427e
.boot 4894208 87e9fd546dded104203a83e7f9099b27
.reloc 16 f7724f363ea796dfafe5a178c57389c5

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: