When Gen Digital acquired Avast, AVG, Norton, and both use AvastCore (Cybercapture) I think avira will use avastcore in future too, but now I find an earth-shattering twist, avira will combination all them's tech. The Avira EPP SDK 1.0.2509 beta version completely overturns the above view, because this version enabled Avast's core local signature library engine, algo64. This algo64 is the new engine launched after Avast acquired AVG, integrating Avast technology, but it is not the original AVG engine, and the signature libraries are not the same.
First, Avast's algo64 engine is referred to as a " low-level antivirus engine " originally named algo, but in the Avira EPP SDK it is named aealgol. Its version is more recent than the Avast algo from six months ago and not much different from the current Avast 25.9, meaning that the low-level antivirus engine integrated by Avira is not significantly behind the original Avast version. aealgol is indeed loaded and activated in the EPP process.
It is worth noting that Avira only integrates a part of the avvps system, the Low Level Antivirus Engine. Other module engines of the Avast avvps system are not integrated, but those are functional module engines, and many functions are already available in the Avira EPP SDK itself. Although there are still some gaps, at least it has the 3A combined technology and BullGuard's Sentryeye proactive defense technology. It is said that the cloud-based WebShield uses Norton's intelligent URL analysis mechanism, although I am not sure whether it comes from Avast or the old Norton's WebShield technology.
Before Avira enables the Low Level Antivirus engine, the avcp-vdf folder is only about 150MB, consisting of 257 files.
After enabling the Low level antivirus engine, new files starting with 'xbva' have appeared in the folder, in addition to the Avira signature files starting with 'xbv'. These are the signature files called by avast's local Low level antivirus engine. The avcp-vdf folder has 119 more files, totaling roughly over 80 MB.
Randomly opening an NMP file clearly shows in its header that it is in the exclusive format of Avast VPS's signature database, so Avira enabling the Avast low-level antivirus engine is a certainty, an indisputable fact.
Moreover, now Avira has adopted Avast's unique method of detecting viruses. Script:SNH-gen ( avira is named TR/SNH )
Isn't this exactly the SNH technology for Avast's script-killing threat? It's just unified under the Avira naming convention. It seems it's not simply about transferring the algo engine and VPS signature database, but truly a deep integration.
In simple terms, Gen has now provided the technology to Avira.
First, Avast's algo64 engine is referred to as a " low-level antivirus engine " originally named algo, but in the Avira EPP SDK it is named aealgol. Its version is more recent than the Avast algo from six months ago and not much different from the current Avast 25.9, meaning that the low-level antivirus engine integrated by Avira is not significantly behind the original Avast version. aealgol is indeed loaded and activated in the EPP process.
It is worth noting that Avira only integrates a part of the avvps system, the Low Level Antivirus Engine. Other module engines of the Avast avvps system are not integrated, but those are functional module engines, and many functions are already available in the Avira EPP SDK itself. Although there are still some gaps, at least it has the 3A combined technology and BullGuard's Sentryeye proactive defense technology. It is said that the cloud-based WebShield uses Norton's intelligent URL analysis mechanism, although I am not sure whether it comes from Avast or the old Norton's WebShield technology.
Before Avira enables the Low Level Antivirus engine, the avcp-vdf folder is only about 150MB, consisting of 257 files.
After enabling the Low level antivirus engine, new files starting with 'xbva' have appeared in the folder, in addition to the Avira signature files starting with 'xbv'. These are the signature files called by avast's local Low level antivirus engine. The avcp-vdf folder has 119 more files, totaling roughly over 80 MB.
Randomly opening an NMP file clearly shows in its header that it is in the exclusive format of Avast VPS's signature database, so Avira enabling the Avast low-level antivirus engine is a certainty, an indisputable fact.
Moreover, now Avira has adopted Avast's unique method of detecting viruses. Script:SNH-gen ( avira is named TR/SNH )
Isn't this exactly the SNH technology for Avast's script-killing threat? It's just unified under the Avira naming convention. It seems it's not simply about transferring the algo engine and VPS signature database, but truly a deep integration.
In simple terms, Gen has now provided the technology to Avira.




