Wabbit - is a small uncommon form of malware and once it infects your computer it can be quite hard to completely remove it because of its self - replicating properties. Here is a little about wabbit, how it works, a couple of major versions of it and ways to protect yourself from possible infection.
A wabbit is a form of malware that continually replicates itself on your computer until it eventually slows and stops it from working. It works not like any other virus or worm and doesn't infect any of your files or documents and does not need a network to spread. Wabbits are known to have bad or malicious side effects on your system as well as a quick capability to multiply.
A version of a wabbit is a fork bomb, a fork bomb is an attack on a system by using a fork function, a fork function in computing is a process where the fork copies itself and becomes a child form of the previous one, which is then in turn called a parent. A fork in more understandable terms is a thread that is multiplied, which can cause great harm to your computer once executed and does a full loop. A fork bomb is something that relies on the numbers of programs and processes, once started, it takes up all available free spots in the list of the system's processes. Once this action has started, a program is no longer able to start until one is stopped, but this is usually a highly unlikely event because that is what the bomb is waiting for. Usually this will cause your computer to become increasingly slow until it just stops working.
Another version of this is a bash fork bomb, it is a simple and small line of eleven characters that wreak great havoc on a computer that has fallen victim to it. The command line for this bomb is simply : ( ) { :l: & }; : creating a no argument base and loops back into itself like the fork bomb up above. In most cases, the main operating system that is most susceptible to it is Unix. In all cases, this bash fork bomb uses a fork function to transmit its havoc in the system. Another version of this command line is (:(){ :|:;}:) though the effects of this is very similar but the parentheses don't cause it to fork off it like the above code, it only affects run from a subshell.
If you are infected by a wabbit or a type of fork bomb there isn't much that you can do to stop it unless you have limitless resources to work on it and usually we don't. If you use another program to rid your computer of the infection it is usually unable to do so because there may be not spots or memory free to run the program. If you have a backup of the system before you were infected then try executing that.
The best method of not being infected by a wabbit or a type of fork bomb is prevention. This can be done by preventing how many processes and programs any user is using at any given time, smaller processes or programs reduce the risk of being attacked by such a pest. Group users are at higher risk of catching the wabbit than a single user has.
Wabbit, even though its an uncommon form of malware, it is real, it's still out there and it still infects and possibly can cripple your computer. Be aware and careful.