GridinSoft Threat Intelligence

savapi3.dll file report

Under review File reputation report
MD5 255dff0d3a393cbb3c20c27ad7794cf2
Latest seen 2023-04-20 23:27:46 (3 years ago)
First seen 2017-09-06 23:10:03 (8 years ago)
Size 434 KB
Product Savapi3 Library

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-09-06 23:10:03 (8 years ago); latest analysis 2023-04-20 23:27:46 (3 years ago).

Publisher context

Company metadata: Avira Operations GmbH @amp; Co. KG. Product metadata: Savapi3 Library.

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.

savapi3.dll is a Windows file recorded in the ThreatInfo database. It is associated with Savapi3 Library. The reported company name is Avira Operations GmbH @amp; Co. KG. The current detection status is Undefined, based on the latest analysis from 2023-04-20 23:27:46 (3 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: Savapi3 Library
Company Name: Avira Operations GmbH @amp; Co. KG
MD5: 255dff0d3a393cbb3c20c27ad7794cf2
Size: 434 KB
First Published: 2017-09-06 23:10:03 (8 years ago)
Latest Published: 2023-04-20 23:27:46 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-04-20 23:27:46 (3 years ago)
%commonappdata%\tencent\qqpcmgr\avira
%programfiles%\tencent\qqpcmgr\11.2.17063.223\avira
%allusersprofile%\\application data\tencent\qqpcmgr\avira
%commonappdata%\tencent\qqpcmgr
%allusersprofile%\\application data\tencent\qqpcmgr
%commonappdata%\innovative solutions

ThreatInfo has observed savapi3.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 7 37.5%
Windows XP 25.0%
Windows Server 2003 12.5%
Windows 8.1 12.5%
Windows 10 12.5%

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

savapi3.dll 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 0x0004a280
Image base 0x10000000

PE Sections:

Sections 5
Raw data 443904

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

.text 302592 bytes · 68.2% of section data
MD5 da354281d10cf4198056376349c318f9
.rdata 115200 bytes · 26.0% of section data
MD5 89d8e115364b416fca405a67ff203484
.data 10752 bytes · 2.4% of section data
MD5 f856608fb718ee5e4854961ecad69721
.rsrc 2048 bytes · 0.5% of section data
MD5 a6c3e6d580631e25173a8c25aa285ddd
.reloc 13312 bytes · 3.0% of section data
MD5 f4fdecb86afae0615fa3b40c22626212

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 255dff0d3a393cbb3c20c27ad7794cf2.
  • 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.