How to Use Stinger
Category : 1
Stinger utilizes next-generation scanning technologies, such as rootkit scanning, and scan performance optimizations.
McAfee Stinger now finds and removes GameOver Zeus and CryptoLocker.
How do you utilize Stinger?
To learn more about GTI File Reputation see the following KB articles
KB 53735 - FAQs for Global Threat Intelligence File Reputation
KB 60224 - The best way to confirm that GTI File Reputation is set up correctly
KB 65525 - Identification generically found malware (International Threat Intelligence detections)
Often Asked Questions
Q: I know I have a virus, but Stinger did not detect one. Why is this?
A: Stinger isn't a substitute for a full anti virus scanner. It's simply supposed to detect and remove certain threats.
Q: Stinger found a virus it could not repair. Why is this?
A: This is probably due to Windows System Restore functionality using a lock to the infected file. Windows/XP/Vista/7 consumers should disable system restore prior to scanning.
Q: Where's your scan log stored and how do I see them?
Inside Stinger, navigate to the log TAB and the logs will be displayed as listing of time stamp, clicking on the log file name opens the file in the HTML format.
Q: How Where are the Quarantine files stored?
This list does not include the results from running a scan.
Q: Why Are there any command-line parameters available when conducting Stinger?
A: Yes, even the command-line parameters are exhibited by going to the help menu inside Stinger.
Q: I ran Stinger and finally have a Stinger.opt record, what is that?
A: When Stinger runs it creates the Stinger.opt document which saves the recent Stinger configuration. When you run Stinger the next time, your prior configuration is used as long as the Stinger.opt document is in precisely the same directory as Stinger.
Is this expected behavior?
A: When the Rootkit scanning alternative is selected within Stinger preferences -- VSCore files (mfehidk.sys & mferkdet.sys) to a McAfee endpoint is going to be updated to 15.x. These documents are set up only if newer than what's on the machine and is needed to scan for today's generation of newer rootkits. In case the rootkit scanning option is disabled inside Stinger -- the VSCore update will not occur.
Q: Does Stinger work rootkit scanning when installed via ePO?
A: We have disabled rootkit scanning from the Stinger-ePO bundle to set a limit on the auto update of VSCore parts as soon as an admin deploys Stinger to tens of thousands of machines. To enable rootkit scanning in ePO style, please use the following parameters while checking in the Stinger bundle in ePO:
--reportpath=%temp% --rootkit
For detailed instructions, please refer to KB 77981
Q: What versions of Windows are supported by Stinger?
A: Windows XP SP2, 2003 SP2, Vista SP1, 2008, 7, 8, 10, 2012, 2016, RS1, RS2, RS3, RS4, RS5, 19H1, 19H2. Moreover, Stinger requires the machine to have Web Explorer 8 or above.
Q: What are the requirements for Stinger to execute in a Win PE surroundings?
A: While creating a custom Windows PE image, add support to HTML Application components using the instructions supplied in this walkthrough.
Q: How do I obtain service for Stinger?
An: Stinger isn't a supported program. McAfee Labs makes no warranties relating to this product.
Q: how How can I add customized detections into Stinger?
A: Stinger gets the option where a user may input upto 1000 MD5 hashes as a customized blacklist. During a system scan, even if any documents match the habit blacklisted hashes - that the files will get deleted and noticed. This attribute is provided to help power users that have isolated a malware sample(s) for which no detection can be found yet from the DAT files or GTI File Reputation. To leverage this feature:
- In the Stinger port goto the Advanced --> Blacklist tab.
- During a scan, all documents which fit the hash is going to have detection name of Stinger! . Full dat repair is put on the file.
- Files that are digitally signed with a valid certificate or people hashes that are marked as blank in GTI File Reputation won't be detected as part of their custom blacklist. This is a security feature to prevent customers from accidentally deleting documents.
Q: How How do conduct Stinger with no Real Protect component becoming installed?
A: The Stinger-ePO package doesn't fulfill Actual Protect. In order to conduct Stinger with no Real Protect getting installed, do Stinger.exe --ePO