GridinSoft Threat Intelligence

savapi.dll file report

Clean record File reputation report
MD5 08e5bf945b032bbfba18dd5bd4421103
Latest seen 2022-03-31 23:52:05 (4 years ago)
First seen 2022-03-26 23:47:58 (4 years ago)
Size 2 MB
Product Savapi Library

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-03-26 23:47:58 (4 years ago); latest analysis 2022-03-31 23:52:05 (4 years ago).

Publisher context

Company metadata: Avira Operations GmbH & Co. KG. Product metadata: Savapi Library.

Digital signature

Signed by Avira Operations GmbH & Co. KG. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

savapi.dll is a Windows file recorded in the ThreatInfo database. It is associated with Savapi Library. The reported company name is Avira Operations GmbH & Co. KG. The current detection status is Clean, based on the latest analysis from 2022-03-31 23:52:05 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Savapi Library
Company Name: Avira Operations GmbH & Co. KG
MD5: 08e5bf945b032bbfba18dd5bd4421103
Size: 2 MB
First Published: 2022-03-26 23:47:58 (4 years ago)
Latest Published: 2022-03-31 23:52:05 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-03-31 23:52:05 (4 years ago)
Signed By: Avira Operations GmbH & Co. KG
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%sysdrive%\rei
%commonappdata%\restoro

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

Windows 10 100.0%

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

savapi.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 0x001f6abd
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2896384

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

.text 2225664 bytes · 76.8% of section data
MD5 0349ef50c124b6d2bf4c3f01354d4387
.rdata 547328 bytes · 18.9% of section data
MD5 16e7e5cdf6754f873f095bc99afaf6d6
.data 37376 bytes · 1.3% of section data
MD5 d502f3b544b734a31e2dc687e2724e91
.rsrc 2048 bytes · 0.1% of section data
MD5 3f8f41bac25466cf5b08d66b55712250
.reloc 83968 bytes · 2.9% of section data
MD5 ba72518b0bea9b8815b9f69e9fd9c233

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 08e5bf945b032bbfba18dd5bd4421103.
  • 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.