GridinSoft Threat Intelligence
savapi.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2019-05-24 03:34:00 (6 years ago); latest analysis 2026-02-04 23:02:18 (3 months ago).
Company metadata: Avira Operations GmbH & Co. KG. Product metadata: Savapi Library.
Signed by Avira Operations GmbH & Co. KG. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
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 2026-02-04 23:02:18 (3 months 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.
File Details
| Product Name: | Savapi Library |
| Company Name: | Avira Operations GmbH & Co. KG |
| MD5: | 918ae6237b909523f0db358702d90b30 |
| Size: | 2 MB |
| First Published: | 2019-05-24 03:34:00 (6 years ago) |
| Latest Published: | 2026-02-04 23:02:18 (3 months ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2026-02-04 23:02:18 (3 months ago) |
Overview
| 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.
Common Places:
| %sysdrive%\rei |
| %commonappdata%\restoro |
| %commonappdata%\restoro\av\avupdate_tmp_n2pxm7\av4\avira603\savapi4lib\win32 |
| %sysdrive%\rei\av\avupdate_tmp_rbvuch\av4\avira613\savapi4lib\win32 |
| %sysdrive%\rei\av\avupdate_tmp_rbvuch\av4\avira612\savapi4lib\win32 |
| %sysdrive%\rei\av\avupdate_tmp_rbvuch\av4\avira614\savapi4lib\win32 |
| %sysdrive%\rei\av\avupdate_tmp_r2wfny\av4\avira616\savapi4lib\win32 |
| %sysdrive%\rei\av\avupdate_tmp_g1iya2\av4\avira628\savapi4lib\win32 |
| %commonappdata%\restoro\av\avupdate_tmp_ukdagk\av4\avira628\savapi4lib\win32 |
| %sysdrive%\rei\av\avupdate_tmp_27ya1s\av4\avira625\savapi4lib\win32 |
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.
Geographic signal
Observed country distribution
ThreatInfo has seen savapi.dll across 82 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 18.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for savapi.dll is Windows 10 with 80.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.
Analysis
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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
a46030b3199e02dad0ef13e56bf5528a
9178df4152f72cb2c4b498bdc67b8ca6
3b25d664947eabd238f4eaec3777a425
78b8207f93599a0fe203e430bbea4d8a
127d66ec64c7e7a09cf48f0ef10ca978
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.