You're asking for help in a criminal activity. Anyone rendering such help will themselves be guilty of a criminal act...

>You're asking for help in a criminal activity.
Technically, writing a virus isn't a criminal activity. Deploying a virus is because it violates the privacy of the target systems. It's irrelevant whether the virus is benign or harmful at that point, but the more damage it does, the worse the crime is.

There are perfectly legitimate (scientific) reasons for writing and studying a virus, but only if it's contained in a clean system owned by the party doing the tests. Unfortunately, that's almost never the intention. :(

>but virii No.
The correct plural of virus is viruses, not virii.

Comments
can u give me some coding for create virus....

I stand corrected in regards to my grammar. Also, I understand that coding a virus is not a criminal activity, but regardless of the legalities, unless someone could prove that their intent is pure (creating a virus removal utility?), there is no way that I will offer any help or support on the subject.

>You're asking for help in a criminal activity.
Technically, writing a virus isn't a criminal activity. Deploying a virus is because it violates the privacy of the target systems. It's irrelevant whether the virus is benign or harmful at that point, but the more damage it does, the worse the crime is.

There are perfectly legitimate (scientific) reasons for writing and studying a virus, but only if it's contained in a clean system owned by the party doing the tests. Unfortunately, that's almost never the intention. :(

>but virii No.
The correct plural of virus is viruses, not virii.

OK!
I understand that asking this question is unusual and virus programming (if it damage someone computer)is criminal activity.but it was just my school project(homework).(you take it very seriously).
I believe that "virus programming" is a knowledge.(and every knowledge can be harmful or useful)
Considering that you don't know me it is logical you don't answer to this question.
but just a question:
if it is criminal activity HOW do you learn this??
and another thing:
In any case I have to (and interested in) finalize my project.
tnx.

It's hard to say where someone learned HOW to make a virus. I mean, where did someone learn how to make Assembly? Where did someone learn how to make a word processor? Some times simply knowing the language and rules you are using you can come up with something on your own. In my past I was bent on writing a Virus, program. Just to write it of course, but I never did. I came close once, I made what I call a bug program. Like giving the computer the flu without damaging it. It caused it to crash but it didn't spread, nor was the damage permanent. It simply sucked up memory like the dickens. And I made it clear what the program was.

Sometimes, all you need is a bit of creativity and extreme knowledge of how a computer and program works. You can design something you never learned to do in the first place. The very first person to make a virus didn't learn how by being taught, but rather discovered how.

And Virus is such a general term. There are many different versions, with many different ideas of what they should do. So you'd need to be more specific. And there are a few sites made for Crackers who like to program virus's. You might want to check these out, though you'd probably hear them calling themselves Hackers so don't search for Crackers.

Oh and make sure you have some hefty Virus and firewall protection. Some of these guys are sick enough to get into each other's computers. No professional curtousy.

Not all Hacker sites are like that luckily. Many of us are just misunderstood.

OK!
I understand that asking this question is unusual and virus programming (if it damage someone computer)is criminal activity.but it was just my school project(homework).(you take it very seriously).
I believe that "virus programming" is a knowledge.(and every knowledge can be harmful or useful)
Considering that you don't know me it is logical you don't answer to this question.
but just a question:
if it is criminal activity HOW do you learn this??
and another thing:
In any case I have to (and interested in) finalize my project.
tnx.

Not all Hacker sites are like that luckily. Many of us are just misunderstood.

Hackers are GOD people! I agree with u.There have been said so much in this, that anyone just a litle comp. enthusiast shouldent confuse hacker with cracker itc.
;)

For virus programming you'll have to dive into system security issues ... see the latest vulnarabilities in various systems and then its your job to program exploits for those vulnarabilities ...

>but it was just my school project(homework).
Writing a virus isn't given as homework. The liabilities are too great for any teaching institution to allow it.

but it can't be so crimminal to just make a litle virus on your own computer that don't goes to other people? Just to make a virus to studing it...
like I want to try.... just see how it works...

Just face it there not gonna help you (not to be mean)


Viruses can't help exicutable programs somtimes but not viruses

>but it can't be so crimminal to just make a litle virus on your own computer that don't goes to other people?
No, it's not.

>like I want to try.... just see how it works...
Unfortunately, nobody will help you even if your intentions are completely benign. When someone wants to write a virus, we have no choice but to assume it's for malicious reasons. If you really want to learn how viruses work, antivirus vendors will typically describe how they work. You can learn to write them by reading those reports and actually learning how your computer works.

HI!
can you guide me about writting viruses in assmbly?
tnx.

If you want a starting point, I would suggest reading "Assembly Language Byte by Byte" written by David Y. Wen and grey G. Whipple. It is rather outdated but pay attention to the sections on file structure and work thru the book line by line, example by example. Much of what you need to know has to come thru experimentation and taking notes and paying attention. Also, learn other languages such as Perl, VBScript, and C. Do not limit yourself to just writing viruses, write Internet Worms and Trojans as well and study books on writing code and strive for excellence and bug free code.

Study examples: Take your virus scanner (but not your firewall) and turn it off. Then hit as many porn sites as you can. Then run your virus scanner and save all of the captured files. Some of the files will be viruses many will be worms and trojans. Use a dissasembler to obtain the source code for the viruses and trojans. The worms will be mostly in VBS which you can study them directly. You may eventually ruin your machine in the process but I have been writing viruses for 15 years and that is the hazards of being a virus coder. Along with studying viruses study the art of hacking and cryptography.

Do not release your viruses. Do not post them on the internet for script kiddies to get a hold of. It is not illegal to write viruses, just illegal to release them. Keep the knowledge to yourself, you may have to protect yourself from the NSA and the black arts of the US government someday which seems to be escalting with the anti-intellectual thinking of George Bush -- though Clinton, brilliant as he is was guilty as well.

Knowledge is power.

This is a good website to review: http://www.spth.de.vu
This gentleman who owns it is from Austria and I admire his skills and attitude a great deal.

Ok, I realize that writing virus's isn't illegal, but the implications that can come on daniweb because of this post are fairly severe, and it is my opinion that this post be deleted, and the thread locked.

>but virii No.
The correct plural of virus is viruses, not virii.

The word virus is latin meaning "of man"... and may not be the correct spelling of virii but implies the "of men".... a direct connection to the hacker language.


Hackers, as a rule, love wordplay and are very conscious and inventive in their use of language. These traits seem to be common in young children, but the conformity-enforcing machine we are pleased to call an educational system bludgeons them out of most of us before adolescence. Thus, linguistic invention in most subcultures of the modern West is a halting and largely unconscious process. Hackers, by contrast, regard slang formation and use as a game to be played for conscious pleasure. Their inventions thus display an almost unique combination of the neotenous enjoyment of language-play with the discrimination of educated and powerful intelligence. Further, the electronic media which knit them together are fluid, `hot' connections, well adapted to both the dissemination of new slang and the ruthless culling of weak and superannuated specimens. The results of this process give us perhaps a uniquely intense and accelerated view of linguistic evolution in action.

Hacker slang also challenges some common linguistic and anthropological assumptions. For example, in the early 1990s it became fashionable to speak of `low-context' versus `high-context' communication, and to classify cultures by the preferred context level of their languages and art forms. It is usually claimed that low-context communication (characterized by precision, clarity, and completeness of self-contained utterances) is typical in cultures which value logic, objectivity, individualism, and competition; by contrast, high-context communication (elliptical, emotive, nuance-filled, multi-modal, heavily coded) is associated with cultures which value subjectivity, consensus, cooperation, and tradition. What then are we to make of hackerdom, which is themed around extremely low-context interaction with computers and exhibits primarily "low-context" values, but cultivates an almost absurdly high-context slang style?

and just to clarify all things.... hacking, cracking, and malicious code writting in any way is illegal in the US of A... as goes for sending eMail, chatting, and any other activity that has the possibility to share information like p2p... even if you are sharing uncopyrighted data (or atleast this is what the government wants).

There are plenty of virii utilities and tutorials on the web....

First though you need to protect the enviroment you wish to work in.

1. Set up a seperate machine with windows 98SE and turn off the GUI launch with Tweak UI

2. Install GoBack (so you can fix all those major screw ups)

3. Never use a floppy that isn't write protected.

4. Do not have the machine networked.

5. Spend lots of time studying asm code for virii before attempting anything.

NEVER use the machine for anything else... I have an old IBM with DOS 5.0 built into the ROM and it is non writable... which makes it a great DOS Virii testing machine... I do not code virii, but I do play with them and try to figure ways to remove them and test command line AV tools on them.

Also before playing with the virii... make sure you have all the AV software on your system removed... and nake a large collection of tools and toys on a CD for your use. This way everything is write protected.

as for where to get the tools, toys and tuts... look on google. Happy hunting and edjumecation (I think that is properly misspelled).

If you want to write code that you are afraid will damage the system you are working on, use a virtual machine. You can install and run many different Operating Systems from within Windows using vmWare. I often use a virtual machine to execute code that may damage the host system. The beautiful thing about virtual machines is they act like an actual computer, but you can reboot them back to a normal state very quickly.

As for writing viruses, most virus writers create the damaging code by accident or focus directly on specific, known exploits. It isn't necessarily hard to write a virus. It is hard to write one that is very good at getting through standard security and propogates very quickly. I would agree that no school would give this as a programming assignment. A teacher may have students create reports about viruses or the people that create them, but I cannot imagine any teacher actually telling a class to write damaging code that they will then grade. If a teacher actually gave that as an assignment, they could be guilty of academic misconduct and be disciplined or terminated.

Sorry to add to an aging thread, but I just had to throw my two cents in.

I'd actually like to write something myself that crashes a computer. Not that I would release it but to learn more about the system and assembly itself.

That's easy to do in Assembly. There's a single command to shut down the system, issue that and your machine will stop dead in its tracks ;)
I leave it up to you to look it up in a manual as I don't have an Asm manual with me.

That's easy to do in Assembly. There's a single command to shut down the system, issue that and your machine will stop dead in its tracks ;)
I leave it up to you to look it up in a manual as I don't have an Asm manual with me.

Sure, but I think maybe have it chew up memory, kill processes on the system, etc. Then at some point have the OS fail (maybe by overwriting the memory it's using?) and crash.

That's easy to do in Assembly. There's a single command to shut down the system, issue that and your machine will stop dead in its tracks ;)
I leave it up to you to look it up in a manual as I don't have an Asm manual with me.

You will not find it in an "asm manual" because it isn't a CPU instruction. You will find it in a Windows API Reference as the "ExitWindows" call (and it can be called from C and Basic programs just as easily). However, non-valid opcodes can cause the CPU to choke (and, no, this isn't as safe or nice as "shutting down the system").

Nathan.

Sure, but I think maybe have it chew up memory, kill processes on the system, etc. Then at some point have the OS fail (maybe by overwriting the memory it's using?) and crash.

Well, if we are talking about Windows, the API does allow you to kill other processes...but you'll need to get their handles first.

Look for the 'winio' package - it might allow you to 'chew up memory' and fail the OS.

Nathan.

well start on windows 98 or windows 95
windows xp could work to but it is easier to get viruses on your system with a windows 98

if you want to earn money for writing a virus
you could try to build one for mac os X
but because it wont run at root you will never be able to
use it on your computer unless you have the SUDO
password

it is fun to mess around on there is a million dollar prize to build a virus that will kill a mac
mainly because experts in mac programming try to
build viruses to kill it all the time but after failing so much
they get tired

but the windows system does give you the perfect viruses
testing system (windows 98) windows xp is a little better but is still junk

I myself have coded 2 virii. You can write them all you want just dont release them. My friend knew a woman who was part of a Russian hacker group. She was arrested and got sentanced for 20 years in prison.

I stand corrected in regards to my grammar. Also, I understand that coding a virus is not a criminal activity, but regardless of the legalities, unless someone could prove that their intent is pure (creating a virus removal utility?), there is no way that I will offer any help or support on the subject.

Hence a disclaimer is in order.

Why [Moderator's edit: Loose the profanity please; it isn't allowed in our forums] should you care if your virus is used ?

by the sounds of it your just trying to think up excuses because you carnt actly program ? .. anyway

Just make one for him and Give him a disclaimer "This was made for educational purposes only. the make "me" is not responsable for what you use it for . by downloading this you accept my yerms and conditions aka disclaimer"

enjoy

Gothika-virus:rolleyes:

Let's not bump old threads for one.... and secondly, it has nothing to do with my ability or inability to write virus code. It has to do with not helping someone to become a pest. I care if someone releases a virus, especially a virus I wrote, that could potentially infect and ruin thousands of machines. Use your head.

I hate it when newbies ask these kinds of stupid questions. I say you lock the topic.

A MESSAGE TO ALL NOOBS:

"Coding viruses" is such a broad way of putting it. Be specific. Think hard about this. Think about how viruses usually work. Read about how they work. Don't come to a forum and embarass yourself.

Take the topic starter of this topic as an example and warning. If you don't want to be looked at as a fool, lazy bum, and illiterate ass, then:

1) post with proper grammar. This isn't AOL, you ass. Act like you know what an article or period is.

2) Explain yourself. Don't leave people out in the desert. Don't you think it would be helpful if we knew what you were talking about or what you want exactly?

Reread this post until you understand where I'm comming from.

This article has been dead for over six months. Start a new discussion instead.