Article View: comp.virus
Article #5262Re: The 1559 Virus (PC)
From: Gonzalo M. Rojas Costa
Date: Fri, 23 Feb 1990 17:33
Date: Fri, 23 Feb 1990 17:33
69 lines
3411 bytes
3411 bytes
Hi
Vesselin Bontchev (T762102@DM0LRZ01.BITNET) writes:
> - The virus is memory resident. It installs itself in the
> memory at address 9800:0000. I couldn't find where (and if)
> it checks for the memory size.
This virus only copies itself to the address 9800h:0000. It don't
installs resident with INT 27 or the function 31H. If I execute a big
program (that ocupies the segment 9800h), this program erase the virus
from memory and a crash will occurr.
Besides, the 1559 virus don't checks the memory size. Then if I
execute a program infected with this virus in a computer with less
than 640K of RAM, the computer hangs. (This efect occurr too, for
example, in an AT with 1024K of memory {512K from factory and 512K of
Extended Memory}).
> - The virus is 1554 bytes long, but may add more bytes (up to
> 1569 I think) to the infected files.
Yes. If I infect a program with this virus, the program don't
grows in a constant quantity of bytes. For that reason I don't find
appropriate the name 1559 for this virus. Besides, the size of the
virus is 1554 bytes. Then I don't find the reason for that name.
> - Only *.COM files greater than 1000 bytes will be infected. I
> couldn't find if there is a limit for the *.EXE ones.
EXE files greater or equal than 3 512-bytes-pages (1536 bytes) are
infected.
> - The first 32 bytes of the *.COM files are overwritten. The
> original 32 bytes can be found at offset (14,15)*16+1015
> from the beginning of the file.
The 32 bytes overwritten can be found at offset (14,15)*16+1271
on the infected program that I disassembled.
(It seems that the offset where the bytes overwritten are located is
(14,15)*16+number, and number depends of the size of the program being
infected).
> - The virus intercepts the WRITE function call (AH == 40H) of
> INT 21h. If the month of the current date is 9 or greater,
> and if the write is on file handle > 4 (i.e., it is a "true"
> file, not stdin/out/err/aux/prn), then the address of the
> memory chunk which has to be written, is increased by 0Ah.
> This leads to garbage being written.
Then, if I type the command COPY myfile1 myfile2 in the months of
September, October, November or December, myfile2 will lose the first
ten bytes, and will add an equal quantity of garbage to the end. (But,
myfile and myfile2 remains of the same size).
An important caracteristic of this virus is that it have
subroutines that don't permit the use of debuggers (such as MSDOS'
DEBUG or Turbo Debugger).
Disclaimer: The views expressed are my own! I do not speak for, nor do
I represent any other person or company.
Gonzalo M. Rojas Costa
BITNET: LISTVIR@USACHVM1
ARPA: LISTVIR%USACHVM1.BITNET@CUNYVM.CUNY.EDU
Owner of ASSMPC-L
Antiviral Research Group
Technical Support Unit
Universidad de Santiago de Chile
Technical Details
Message-ID:
<0013.9002231213.AA10580@ge.sei.cmu.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!jarthur!polyslo!vlsi3b15!vax1.cc.lehigh.edu!sei.cmu.edu!krvwShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!jarthur!polyslo!vlsi3b15!vax1.cc.lehigh.edu!sei.cmu.edu!krvw From: LISTVIR@USACHVM1.BITNET (Gonzalo M. Rojas Costa) Newsgroups: comp.virus Subject: Re: The 1559 Virus (PC) Message-ID: <0013.9002231213.AA10580@ge.sei.cmu.edu> Date: 23 Feb 90 17:33:30 GMT Sender: Virus Discussion List <VIRUS-L@IBM1.CC.Lehigh.EDU> Lines: 69 Approved: krvw@sei.cmu.edu