Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more ➡
Standard view
Full view
of .
Add note
Save to My Library
Sync to mobile
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
How to Write a Virus Program_begginers

How to Write a Virus Program_begginers



|Views: 56,439|Likes:
Published by Still Bligha
Still want to learn virus Philosphy..::yao:: this is for begginers but you need more computer architecture technics...
Still want to learn virus Philosphy..::yao:: this is for begginers but you need more computer architecture technics...

More info:

Published by: Still Bligha on Nov 12, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See More
See less





From AlGerIA With L0V3
byThe Cheshire Cat!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!For people who have nothing else to do but cause unprecidented havocon other peoples systems, this is something you should read. To beginwith, I'd like to explain briefly to the ignorant readers of this, whatexactly a virus program is. A virus program is in the genre of tapeworm,leech, and other such nasty programs. I will show clearly, one possibleapplication of it, on an Apple system, and I will demonstrate how easilythis little pest could lead to wiping out most of someone's importantdisks. Here we go!One day, while I had little else to do, I was reading an computingarticle in some obscure science magazine. As it happened, the articlediscussed a growing problem in the computer community about the dangerof virus programs. Someone quoted in the article said that they wrotea very simple virus program and put it on the univerisity computer asa test. All the program did was l}iook through the computers memory,and devices (tape drives, hard drives, etc...) for stored programs, andwhen it found one, it would search through the program for itself. Ifit didn't find anything, it would find an empty spot in the program, andimplant itself. This may not sound too exciting, but this little programwas actually part of another program (maybe a word processor, or spread-sheet, or maybe even zaxxon) and whenever someone ran that program, andexecuted the little virus stuck inside it, the virus would stop programexecution (for a time period that even us humans wouldn't notice) and doits little job of infecting other programs with itself. This exampleof a virus was harmless, but even so, after only 4 hours the whole systemhad to be shutdown and the whole memory core dumped because the virus hadbegun to fill up too much space and it was using up all the mainframe'stime. I don't think it would have been so easy if this professor hadjust done this experiment on his own and had not got permission or toldanyone about it. Think of the havoc!!Well, that has taken up too much time discussing already, so I'lladd only one more thing before we get down to business, that REALviruses are extemely BAD. They usually are designed as time bombs thatstart erasing disks, memory, and maybe even backups or the operatingsystem after they have been run so many times, or after a certain dateis reached. Someone did this to a bank one time (and by the way he wasnever caught!) He was given the task of designing their operating systemand security, and he decided he wasn't getting paid enough, so he devisedhis own method of compensation. Every so often, the computer would steala certain amount of money from the bank (by just CREATING it electronic-ally) and would put it in an account that didn't exist as far as the bankor the IRS or anybody knew, and whenever this guy wanted, he went tothe bank and withdrew some money. They aren't sure how he did it, buthe probably visited the electronic teller as often as possible. As Isaid, the authorities still haven't found him, but after several yearsof his leech program being in service, it "expired." They assume thathe set it up to destroy itself after so long, and when this littleprogram was gone, the bank suddenly was missing several million dollars.Now, I wouldn't recommend doing this sort of thing, but then again, whosaid crime doesn't pay?Now to discuss the application of this to a Personal Computer isvery simple. When I decided to do this, I figured it would be easiestto stick my program in the DOS, so that I would always know where to putanother copy of my virus while it was reproducing itself, and that it
would be easier to explain why the disk drive is running when it startsto initialize your disks. For those who have a copy of Beneath Apple DOSit would be easy to find the space to put in the program. If you don't,I tell you a few places that are not used (or where you can put it andit won't be noticed) but I'd recommend getting the book anyways - it'san excellent tool for doing these sort of things, and useful even if youdon't. As suggestions for where to put it (if you choose to infect DOS),you could use BCDF-BCFF which is still unused, or BFD9-BFFF, which WASunused, but has since been used in updates of DOS. Likewise, I wouldalso suggest using space taken up by junk like LOCK or UNLOCK commands.Who the hell ever uses them? Think about it, when was the last time youused the lock command? Get real. If you don't like that, how aboutMAXFILES. I've only used that in a program once in my entire life. Iknow people who couldn't even tell you what it does. That would make mefeel safe about sticking a virus there.But now comes the part that will be harder for the inexperienced,but easier as long as you know what you're doing. By the way, you'vebeen TOTALLY wasting your time reading this if you don't understandassembly, because you HAVE TO in order to accomplish a task such as this.But, don't fret, you could insert a little BASIC code into some dumbutility (like an program whose only function is to initialize disks) thatwould put itself on the disk, as it initializes it (probably as the helloprogram) and would work from that aspect. Of course, it would be easierfor a less experienced person to detect, but who really cares!As I was saying, however, you now have to write the code. If youwork in an area where you are limited memorywise (like I did) it can gettough at times. The only way I got through it was by referring todocumented listings of all of DOS that I got somewhere, and using bitsand pieces of routines from other things as much as I could. When Iwas done, I had a copy of DOS that when it was booted into the computer,would work completely properly (except for maybe some bizarre circum-stances that I didn't bother testing for), but when someone CATALOGed adisk, it did a few different things. It would first load up the VTOC asusual, but then it would jump to MY routine. In this instance, it wasvery easy to use the VTOC which contains many unused bytes to house mycounter. I would increment it, check if it was time to destroy the disk,and then execute an INIT, or just save the VTOC. Then it would savethree more sectors to the disk. One was the place where DOS branched tomy routines, the others were my actual routine. And thus was born avirus. I guarentee that if anyone has experienced a problem with theirdisks, it was not my fault because I have not yet implemented the virus.No one has pissed me off enough to warrant its use. Even worse is thefact that it could backfire (after being distributed across the country,I don't doubt I'd end up with it also) because not only was it very wellplanned, but you don't even notice any sort of a pause. The virusexecutes itself so fast that there is little more than a microsecond ofa pause while the catalog is going on. I tried comparing it to a normalcatalog, and found I couldn't tell the difference. The only way thisthing wouldn't work is if the disk it was cataloging wasn't DOS 3.3, andif that happened, it would probably screw the disk anyways. I knowthere are people who will abuse this knowledge, so you may wonder why Ieven bothered writing it. The fact is that it isn't important to shieldpeople from this knowledge, what is important is for people to know thatcan be done, and perhaps find a way to prevent it. Just consider whatwould happen if someone starting putting a virus in a DDD ][.2. First ofall, everyone would get a copy of it and use it. Only a few would bethat interested to check what these new updates to it were. And perhapswithin a month, whenever you tried to unpack a program, it would insteadinitialize the disk with your file on it. So, like I said, beware ofthose that would jeapordize themselves and would do such a thing. Ofcourse, I wouldn't hesitate to drop my "bomb" on a few leech friends ofmine who don't have modems, but thats a different story. I don't haveto worry too much about getting the "cold" back from them. They'll betoo screwed up to worry about trading disks. Well, I've said too much

Activity (49)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
masslibrary added this note|
Varun Sharma liked this
Sundareswaram Pv liked this
Sundareswaram Pv liked this
Sundareswaram Pv liked this
BSASciti liked this
Sundareswaram Pv liked this
masslibrary liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->