Article View: comp.virus
Article #3109Re: Comment on the MtE wars (PC)
From: Kevin Marcus
Date: Mon, 09 Nov 1992 23:25
Date: Mon, 09 Nov 1992 23:25
14 lines
1069 bytes
1069 bytes
Hmm. MtE detection is difficult, but there are a few things that one can look out for in order to help you get a staart if you are writing an MtE detector, without having "big labs" and stuff. One, as someone kindly pointed out at one time, I forgot where I saw it, but the MtE can only generate certain code. It can't generate a variety of instructions, and any program which begins with these instructions cannot possibly be infected. Two, the MtE always has certain markers. For example, the end of the decrypting algorythm always ends with JNZ. If you have a disasssembler, or even debug, you can spend a few hours and figure out how to take care of a variety of infections.
Technical Details
Message-ID:
<0002.9211121928.AA09892@barnabas.cert.org>Path:
arc1-ca.pugleaf.net!sparky!uunet!ukma!usenet.ins.cwru.edu!cert!netnews.upenn.edu!netnews.cc.lehigh.edu!newsShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!ukma!usenet.ins.cwru.edu!cert!netnews.upenn.edu!netnews.cc.lehigh.edu!news From: tck@fold.ucsd.edu (Kevin Marcus) Newsgroups: comp.virus Subject: Re: Comment on the MtE wars (PC) Message-ID: <0002.9211121928.AA09892@barnabas.cert.org> Date: 9 Nov 92 23:25:59 GMT Sender: virus-l@lehigh.edu Lines: 14 Approved: news@netnews.cc.lehigh.edu