GridinSoft Threat Intelligence
avipbb.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-03-28 13:05:33 (8 years ago); latest analysis 2023-04-09 23:58:46 (3 years ago).
Company metadata: Avira Operations GmbH @amp; Co. KG. Product metadata: Avira Product Family.
Signed by Avira Operations GmbH @amp; Co. KG. The signature is reported as valid, but signed files can still be bundled or abused.
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
avipbb.sys is a Windows file recorded in the ThreatInfo database. It is associated with Avira Product Family. The reported company name is Avira Operations GmbH @amp; Co. KG. The current detection status is Clean, based on the latest analysis from 2023-04-09 23:58:46 (3 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.
File Details
| Product Name: | Avira Product Family |
| Company Name: | Avira Operations GmbH @amp; Co. KG |
| MD5: | b137ebfd940f3bdc86d53ff78c5bffd2 |
| Size: | 141 KB |
| First Published: | 2018-03-28 13:05:33 (8 years ago) |
| Latest Published: | 2023-04-09 23:58:46 (3 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2023-04-09 23:58:46 (3 years ago) |
Overview
| Signed By: | Avira Operations GmbH @amp; Co. KG |
| Status: | Valid |
The signature on avipbb.sys 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.
Common Places:
| %programfiles%\totalav\savapi\on_access\win64 |
| %programfiles%\pcprotect\savapi\on_access\win64 |
| %programfiles%\scanguard\savapi\on_access\win64 |
| %sysdrive%\programmi\totalav\savapi\on_access\win64 |
| %programfiles%\totalav\updates\savapi 3.0.0\on_access\win64 |
| %sysdrive%\archivos de programa\totalav\savapi\on_access\win64 |
ThreatInfo has observed avipbb.sys 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 avipbb.sys across 69 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 21.9% 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 avipbb.sys is Windows 10 with 77.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
avipbb.sys is identified as pe for 64-bit systems. The subsystem is Native. 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.
26470eb860fd0f2b26464f5427b98516
5cf100bdc816ced681d1831fa88d3104
ea622d6a57e7c9e5e5a6772829855771
8cbe325674ca648c42b1b597a6539ac9
b80289e2fd895e54ce10ce077214ba02
d36d607a2f94ad31c27f623e689ff359
3991516336e8c7daff1f893c775cf768
e1e01707598774480a0c73584f85c721
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.