XylentAntivirus
Level 3
- May 9, 2024
- 101
The issue is actually hashes. There too many hashes at there and it's fully localized. If you want I can create lite edition. The lite edition is keep heuristics, is most power come from there. No Virusshare undefinied hashes. No old hashes older than 1 year (securiteinfoold.hdb). With this most of issues should be fixed but if you want I can create more lite edition.I've just tested it quickly, even though you haven't updated it yet and, for the moment, too many things need to be revised...
For the record, Xylent is an antivirus project based on ClamAV. It also uses MD5 and SHA1 rules from MalShare, VirusShare, VirusSign etc., as well as YARA.
The file is 1.4GB in size, installs and... doesn't launch... I launch it directly in admin. (xylent_antivirus.exe & engine.exe )
The product consumes a lot of Ram... Between 2GB and 5GB of RAM! That's huge!!!
View attachment 283320View attachment 283321
Xylent create no registry key at startup. In case of infection, the antivirus will not protect you. Why is this? Because there's no entry at startup... a shame for an AV...
View attachment 283322
Xylent tries to create YARA rules with Powershell. Only errors...
View attachment 283323
Obviously, with so much RAM monopolized by Xylent, the VM crashed. Either the AMD graphics driver crashed, or... BSOD (I had both)
There's definitely a problem with the anti-virus and an optimization problem.
For the moment, I won't test it. To be reworked!
Last edited: