McAfee Labs Stinger
Stinger is a stand-alone utility used to detect and remove specific viruses. It is not a substitute for full anti-virus protection, but rather a tool to assist administrators and users when dealing with an infected system. Stinger utilizes next generation scan engine technology, including process scanning, digitally signed DAT files, and scan performance optimizations.
How do I use Stinger?
The Stinger for W32/Polip can be found here
- Download
v10.0.1.688 [5,207,047 bytes] (11/23/2009)
- This version of Stinger includes detection for all known variants, as of
November 23rd, 2009:
- Detects and removes threats identified here
- When prompted, choose to save the file to a convenient location on your
hard disk (such as your Desktop folder).
- When the download is complete, navigate to the folder that contains the
downloaded Stinger file, and run it. WindowsME/XP/Vista users read
this first.
- The Stinger interface will be displayed.
- If necessary, click the Add or Browse
button to add additional drives/directories to scan. By default the C: drive
will be scanned.
- Click the Scan Now button to begin scanning the specified
drives/directories.
- By default, Stinger will repair all infected files found.
- To enable Artemis Technology in stinger click on preferences and then select
the required sensitivity level. If you select "High" or "Very High" McAfee Labs
recommends that you set the "On virus detection" action to "Report only" for the first scan.
To learn more about Artemis see the following KB articles
KB53735 - How does McAfee Artemis technology improve malware detection
KB60224 - Artemis and your information
KB65525 - Artemis Detections and submitting samples
Frequently Asked Questions
- What is the List Viruses button used for?
- A list of the viruses that stinger is configured to detect is displayed when pressing the List Viruses
button. This virus list does not contain the results from running a scan.
- How do I save the scan results to a log file?
- Click the File menu and select Save report to file
- I know I have a virus, but Stinger did not detect one. Why is this?
- Stinger is not a substitute for a full anti-virus scanner. It is only designed to detect and remove specific threats.
- How can I get support for Stinger?
- Stinger is not a supported application. McAfee Labs makes no guarantees about this product.
- Stinger found a virus that it couldn't repair. Why is this?
- This is most likely due to Windows System Restore functionality having a lock on the infected file. WindowsME/XP users should disable system restore
prior to scanning./li>
- Are there any command-line parameters available when running Stinger?
- Yes, the parameters are displayed when passing Stinger the /? switch:
- /ADL - Scan all local drives.
- /GO - Start scanning immediately.
- /LOG - Save the log file after scans.
- /SILENT
- Do not display graphical interface.
- I ran Stinger and now have a Stinger.opt file, what is that?
- When Stinger runs it creates the Stinger.opt file that saves the current Stinger configuration. This way when you run Stinger the next time your previous configuration is what is used, as long as the Stinger.opt file is in the same directory as Stinger
- Where can I send feedback to regarding Stinger?
Update History
- 2/02/2009
- Removal of ePO-supported Stinger tools
- 11/22/2008
- Updated version information, added W32/Autorun variants
- 9/10/2007
- Updated version information, variants, and extended expiration date
- 4/05/2006
- Updated version information, and extended expiration date
- 2/02/2006
- 10/05/2005
- Added W32/Bagle.cc - .dd
- Added W32/Bropia.worm.bx/by
- Added W32/Korgo.worm.aj
- Added W32/Lovgate.ar@MM
- Added W32/Mydoom.bw@MM
- Added W32/Sober.r@MM
- Added W32/Zafi.e@MM
- Changed default download name to "s_t_i_n_g_e_r.exe" as Sober.r terminates
"stinger" based process names
- 8/17/2005
- Added Stinger 2.5.6 for ePO
- 8/16/2005
- Added W32/IRCBot.worm family (includes W32/IRCBot.worm!MS05-039)
- Added W32/Zobot.worm family
- 5/03/2005
- Changed default download name to "s-t-i-n-g-e-r.exe" as Sober.p terminates
"stinger" based process names
- 5/02/2005
- Added W32/Bagle.bo - bt@MM
- Added W32/Bropia.worm.q - aj
- Added W32/Sober.m - .p@MM
- Changed default download name to ST1NGER.EXE as Sober.p terminates "stinger"
based process names
- 3/01/2005
- Added W32/Bagle.dldr
- Added W32/Bagle.bi - bn@MM
- Added W32/Bropia.worm.q - .u
- Added W32/Mydoom.bf - bi@MM
- 2/21/2005
- Added W32/Mydoom.be@MM
- Added W32/Sober.l@MM
- 2/18/2005
- Added W32/Mydoom.bc - bd@MM
- Added W32/Bropia.worm.a - .p
- 2/16/2005
- Added W32/Bagle.bh - bm@MM
- Added W32/Dumaru.bd - bg@MM
- Added W32/Mydoom.ao - bb@MM
- Added W32/Nimda.u@MM
- 1/03/2005
- Increased expiration date
- 12/14/2004
- Added W32/Zafi.d@MM
- Added Exploit-Lsass
- Added W32/Bagle.bf - .bg@MM
- Added W32/Korgo.ag - .ai
- Added W32/Mydoom.an@MM
- Renamed BackDoor-CHR -> BackDoor-CEB
- 11/22/2004
- Posted ePO version 2.4.5.1
- 11/19/2004
- Posted version 2.4.5.1 to correct an incorrect identificaion issue
- 11/19/2004
- 11/8/2004
- Added W32/Bugbear.j@MM
- Added W32/Korgo.worm.aa.dam
- Added W32/Korgo.worm.ac.dam
- Added W32/Korgo.worm.ae
- Added W32/Lovgate.aq@MM
- Added W32/Mydoom.ad - .ah@MM
- Added W32/Pate.d
- Added W32/Sasser.worm.g
- 10/29/2004
- Stinger configured to scan all files by default
- Added W32/Bagle.ba - .bd@MM
- Added W32/Netsky.ah - .ai@MM
- Added W32/Zafi.c@MM
- 10/14/2004
- 9/28/2004
- Added W32/Bagle.ar - .az@MM
- Added W32/Dumaru.aw - .bb@MM
- Added W32/Korgo.w - .ad
- Added W32/Lovgate.ap@MM
- Added W32/Mydoom.t - .ac@MM
- Added W32/Nachi.worm.m
- 8/17/2004
- 8/16/2004
- Added W32/Mydoom.s@MM
- Added Backdoor-CHR
- 8/9/2004
- Added W32/Bagle.aj - .aq@MM
- Added W32/Lovgate.al - .am@MM
- Added W32/Mydoom.p - .r@MM
- 7/30/2004
- 7/28/2004
- 7/26/2004
- 7/19/2004
- Added W32/Bagle.ai@mm
- Added W32/Mydoom.n@mm
- Added W32/Lovgate.ae - .ak@mm
- 7/18/2004
- Added W32/Bagle.ag - .ah@mm
- 7/16/2004
- Added W32/Bagle.ad - .af@mm
- 7/02/2004
- Added W32/Korgo.worm.p - .v
- Added W32/Lovgate.ac@MM - .ad@MM
- Added W32/Mydoom.l@MM - .m@MM
- 6/14/2004
- Added W32/Korgo.worm.a - .o
- Added W32/Zafi.a@MM - .b@MM
- 5/19/2004
- Posted ePO Stinger version 2.2.7
- 5/18/2004
- Added W32/Bagle.ac@MM
- Added W32/Dumaru.aj - .ap
- Added W32/Lovgate.ab@MM
- Added W32/Mydoom.k@MM
- Added W32/Sasser.worm.f
- Added W32/Sober.g@MM
- 5/10/2004
- Added W32/Bagle.ab@MM
- Added W32/Netsky.ac - ad@MM
- Added W32/Sasser.worm.e
- 5/04/2004
- 5/03/2004
- Posted ePO Stinger v2.2.4
- 5/02/2004
- Added W32/Sasser.worm.b - .c
- 4/30/2004
- 4/28/2004
- Added W32/Bagle.aa@MM
- Added W32/Netsky.aa - .ab@MM
- 4/26/2004
- Added W32/Bagle.x - .z@MM
- Added W32/Bugbear.c - .d@MM
- Added W32/Doomjuice.c
- Added W32/Dumaru.ae - .ah@MM
- Added W32/Elkern.cav.f
- Added W32/Lovgate.z@MM
- Added W32/Mimail.v@MM
- Added W32/Mydoom.i - .j@MM
- Added W32/Netsky.u - .z@MM
- Added W32/Yaha.aa@MM
- 4/6/2004
- Added W32/Netsky.s - .t@MM
- Added W32/Lovgate.n - .y@MM
- 4/4/2004
- 3/29/2004
- 3/26/2004
- 3/22/2004
- Added W32/Netsky.o - .p@MM
- Added W32/Bagle.r - .t@MM
- Added W32/Mydoom.h@MM
- 3/15/2004
- Added W32/Bagle.o - .p@MM
- Added W32/Netsky.k - .n@MM
- 3/13/2004
- Added W32/Bagle.k - .n@MM
- 3/9/2004 2:25pm pst
- 3/8/2004 2:25pm pst
- 3/3/2004
- 3/3/2004
- 3/2/2004
- Added W32/Bagle.f - .j@MM
- Added W32/Mydoom.g@MM
- 3/1/2004
- 2/29/2004
- 2/27/2004
- 2/25/2004
- Added W32/Netsky.c@MM
- Posted ePO Version 2.0.4
- 2/24/2004
- 2/23/2004
- 2/18/2004
- Added W32/Netsky.a@MM & W32/Netsky.b@MM
- Posted ePO Version 2.0.2
- 2/17/2004
- Added W32/Bagle.b@MM, W32/Doomjuice.worm
- Updated Sdbot, Deborm, Mimail, and Nachi
- Renamed W32/Lovsan.worm -> W32/Blaster.worm
- Renamed W32/Dfcsvc.worm -> W32/Anig.worm
- Posted ePO Version 2.0.1
- 1/30/2004
- 1/29/2004
- Added W32/Mymail.s@MM
- Added W32/Dfcsvc.worm
- 1/28/2004
- Added W32/MyDoom.b@MM
- Posted ePO version 1.9.9
- 1/27/2004
- Enhanced W32/Mydoom@MM repair to remove reboot dependency during the
repair process.
- Posted ePO version 1.9.7
- 1/26/2004
- Added W32/MyDoom@MM *Note that a reboot is required after running Stinger
for a complete clean
- Added W32/Dumaru.y@MM - .aa@MM
- Updated Mimail with the latest additions
- 1/20/2004
- 1/18/2004
- 12/22/2003
- 12/21/2003
- Added W32/Sober.c@MM, W32/Mimail.j - .o
- 12/18/2003
- 11/14/2003
- 11/11/2003
- Enhanced W32/Sober@MM repair
- 10/31/2003
-
10/28/2003
- Added W32/Sober@MM,
W32/Dumaru.o - .r
10/10/2003
- Added W32/Pate,
W32/Dumaru.e - .m
10/01/2003
- Posted version 1.8.7 with new expiration date
- Posted ePO version 1.8.7
9/25/2003
9/19/2003
- Added W32/Swen@MM, W32/Yaha.x@MM and W32/Yaha.y@MM
8/28/2003
- Added W32/Dumaru.b - .d and PWS-Narod, Posted ePO version 1.8.5
8/19/2003
- Added W32/Dumaru@MM, W32/Sobig.f@MM
8/18/2003
- Added W32/Nachi.worm, W32/Lovsan.worm.d
8/15/2003
8/14/2003
- Corrected issue, which prevented W32/Lovsan.worm.a from being repaired
properly
8/13/2003
- Added Exploit-DcomRpc, W32/Lovsan.worm.a & .b, and generic W32/Lovsan.worm
to version 1.8.1, posted ePO version 1.8.0
8/11/2003
8/01/2003
- Added W32/Mimail@MM, posted ePO version 1.7.9
7/30/2003
- Added IRC/Flood.ap, IRC/Flood.bi, IRC/Flood.cd, W32/Sdbot.worm.gen,
and W32/MoFei.worm
7/21/2003
- Added W32/Deborm.worm.gen
7/03/2003
7/02/2003
- Added W32/Mumu.worm.b and PWS-Sincom
6/25/2003
- Added W32/Sobig@MM variants
6/20/2003
- Minor detection name correction
6/19/2003
- Added Bat/Mumu.worm, IPCScan trojan, NTServiceLoader trojan, PCGhost
application, RemoteProcesslLaunch application, W32/Lovgate.n@M, and W32/Yaha.t@MM
- .u@MM
6/5/2003
5/16/2003
- Added W32/Lovgate.j@M through .m@M
- Resolved an issue where Stinger was not preserving the last access date
on files.
- Posted ePO Deployable version of Stinger 1.6
5/12/2003
- Added W32/Fizzer@MM and W32/Yaha.s@MM
4/14/2003
- Added W32/Lovgate.e@M - W32/Lovgate.g@M, updated BackDoor-AQJ detection,
W32/Yaha.m@MM - W32/Yaha.r@MM
- Includes self-validation integrity check
2/26/2003
- Added W32/Lovgate.a@M - W32/Lovgate.d@M, BackDoor-AQJ, W32/Sircam@MM,
W32/Funlove@MM, and W32/Nimda.a@MM - W32/Nimda.q@MM
2/14/2003
- Posted EPO deployable version of Stinger.exe
1/25/2003
- Added W32/SQLSlammer.worm and name detection for W32/Lirva.c@MM
1/08/2003
- Added W32/Lirva.a@MM and W32/Yaha.m@MM
12/30/2002
- Added W32/Yaha.a@MM - W32/Yaha.l@MM
- DAT files are now stored in the executable
10/09/2002
- Removed Rwabs.dll dependency as it caused problems for users who had
very old versions of the scan engine installed
- Allows users to enter a drive letter or driver letter: when configuring
Stinger to scan for additional drives
- Clarified the purpose of the List Viruses button
10/04/2002
- Reposted package as self-extracting archive instead of .zip archive,
updated DAT files to include detection for corrupted W32/Bugbear.dam files.