Avast WEBforum
Other => Viruses and worms => Topic started by: Howard9 on September 10, 2017, 02:44:19 PM
-
McAfee® Labs Stinger™ Version 12.1.0.2478 built on Sep 8 2017 at 02:32:19
Copyright© 2015, McAfee, Inc. All Rights Reserved.
AV Engine version v5900.7806 for Windows.
Virus data file v1000.0 created on Sep 8, 2017
Ready to scan for 10212 viruses, trojans and variants.
Custom scan initiated on Saturday, September 09, 2017 10:37:07
C:\Program Files (x86)\Vistumbler\UpdateManufactures.exe [MD5:89991851e7075016cc0c9470df431755] is infected with Artemis!89991851E707
C:\Program Files (x86)\Vistumbler\UpdateManufactures.exe has been Deleted
C:\Program Files (x86)\Vistumbler\vistumbler_updater.exe [MD5:baf5334cd2691d4b9f90960f26cfe5f7] is infected with Artemis!BAF5334CD269
C:\Program Files (x86)\Vistumbler\vistumbler_updater.exe has been Deleted
Summary Report on C:
F:
File(s)
TotalFiles:............ 1605845
Clean:................. 498909
Not Scanned:........... 1106934
Possibly Infected:..... 2
Time: 18:28:05
Scan completed on Sunday, September 10, 2017 05:05:12
-
You can report suspicious/malicious files here: https://www.avast.com/report-malicious-file.php
-
As it say ( Possibly Infected:..... 2)
McAfee Artemis is a behavior detection, so if the file has behavior similar to a malicious file it may trigger detection
all detections here are behaviour (Gen.....)
https://www.virustotal.com/#/file/7a3ef7981630658a46148268c3252913a568bb9b2c09ddf28d16b2cd56ae8965/detection
https://www.virustotal.com/#/file/606917438d8cf8b95bde0f99d58ffdb8b3a5ebe5edceb07404f4eff95b65d0b8/detection
Do you have a program called Vistumbler installed?
Vistumbler >> https://www.vistumbler.net/
Why did you run McAfee stinger, do you have a problem?
-
And this is what F-Secure lab say
===============================================================================================
Thank you for your submission.
Our analysis indicate that the file you submitted is clean.
Our security product recently had a False Positive related to this file and the issue was fixed in a later database update.
===============================================================================================