5 Replies Latest reply on May 1, 2012 12:56 PM by rb78

    mciptshm.dll

      Hi,

      McAfee has found a trojan (Artemis!.....etc) in one of its own files (MCIPTSHM.DLL). Now McAfee still works (after putting the file in quarantine), and searching for the file on internet didn't reveal any suspected problems. Anybody else has a similar experience with this file? (Virusscan 15.0.300 datfile 6696). What properties should this file (size, date, etc) have?

        • 1. Re: mciptshm.dll
          Dinz

          Hi All,

           

          Could you please let us know the version of your McAfee Virus scan version & DAT.

           

          My bad , Just noticed the versions . . .This has been reported to the concerned team & we shall get back to you asap

           

           

          Thanks,

           

          Message was edited by: Dinz on 4/30/12 2:04:46 PM GMT-06:00
          • 2. Re: mciptshm.dll
            dougr_t3_support

            We have reproduced this issue and made the necessary changes in the database to prevent future detections of this file. Please let me know if you are still having any issues.

             

            Regards,

            • 3. Re: mciptshm.dll

              Hi,

               

              I'm having the same issue. First I got a popup message from Mcafee AntiVirus that my system is at risk then did a FULL scan of my PC and found Artemis!226F985A2463(Trojan) but it cannot be removed. What's happening?

               

              Please help.

               

              Thanks.

              • 4. Re: mciptshm.dll
                Vinod R

                Are you sure its the very same file?-- the detection name is generic(system generated algorithm) do not go by that.... just right click McAfee icon on taskbar and update..

                 

                Once done. restart your computer.. and rescan the PC.. get the exact file name and path along with the detection name in the next post.

                • 5. Re: mciptshm.dll

                  I see the file back in the directory again and virusscan works as expected. So this looks solved, thanks