WARNING THE FOLLOWING COMMANDS ARE DANGEROUS!


Assuming /dev/hda is the block device corresponding to the master drive on the primary IDE interface, it will be wiped in quick mode (option -q) i.e. with four random passes. The inode won't be renamed or unlinked (option -k). Before starting, it will ask you to type ``yes''.

This is kind of like Format C:\ on Windows.

Delete all files, delete current directory, and delete visible files in current directory. It's quite obvious why these commands can be dangerous to execute and for them to take full destructive effect they should be executed as the super-user (SUDO)


Reformat: Data on device mentioned after the mkfs command will be destroyed and replaced with a blank filesystem.


Block device manipulation: Causes raw data to be written to a block device. Often times this will clobber the file-system and cause total loss of data:


Fork-bomb: Executes a huge number of processes until system freezes, forcing you to do a hard reset which may cause corruption & Data damage

In Bash: (This thing looks really intriguing and curiosity provokes)


In Perl


These are not at all comprehensive and you should not use this as a checklist to determine if a command is dangerous or not but be assured most of the above will screw your Linux File-system in approx 10 seconds flat.

To find out if its /dev/hda or /dev/sda on your system, use a partition editor like GParted and make a mental note of which device is your primary block-device.

Lastly a command that most of you will find useful at some stage of your hacking career. Completely erase that pesky history file!

Now there is absolutely no record of who did what, when or where. In most of the above instances all that gets left behind is a flashing cursor with the legend "File Not Found!" or "BOOT DISK FAILURE"

If you have friends that like to use SSH, Putty & SSL-Client here's something that will completely screw with there head.

SSLCat is a netcat like utility with SSL support. SSLCat is a simple Unix utility that reads and writes data across an SSL enabled network connection.

It takes data from STDIN and prints it to STDOUT.

echo 'HEAD / HTTP/1.0\r\n\r\n' | sslcat Victims-IP | grep ^Server

As they login to there Secure Shell Session they suddenly see it flash across the terminal echo "HEY BUDDY, I'M INSIDE YOUR HARD-DISK"

If args are supplied, they are passed to the ssl-client unmodified. (NASTY!) This would mean you can pipe something like the following into there SSH Session.

Where "sn!.sg!+" is simply rm -rf * shifted a character up, lets hope they where not logged in as root, if they where they may not have a Job for much longer!