How To Remove Gphone Virus
Well gphone.exe is nowadays one of the most dangerous virus spreading very rapidly. It is a Trojan and changes your IE homepage and sends tries to open gtalk and yahoo messenger. It even sends messages to gtalk contacts. Its icon is just like that of folder icon and people thinking of folder click on it get infected by the virus. Gphone virus basically is a 260 kb .exe file which looks like a folder and it can take any name of any other folder if you have clicked on the virus folder which looks like a folder but it is not. If you have a folder name ―movies‖ in your D drive it will make a exe file in the folder named movies.exe and if you click on that exe file it too work as a virus. It makes .exe files in all the folders you have with the name of the folder. How to remove this virus Method 1
1. Go to Task Manager then Processes and then click on gphone.exe and click on end process. 2. Manually go to folder where gphone.exe is present and delete it.
35
Method 2 Use the Glary Utilities freeware to remove the exe files. 1. Install the Glary Utilities. Open it 2. Go to the modules tab -> Files and Folders-> Duplicate files finder. 3. Search for .exe files of same size and delete all the files with size 260 kb.
Rahul‟s Suggesion:- “You can download the Glary Utilities from my website www.ethicalhacking.do.am free of cost.”
36
Common Methods For Hacking Any Website
Starting from the base, Gone days when website hacking was a sophisticated art, and I was in 10th standard when I heard that Ankit Fadia hacks into CHIP magazine website but today any body can access hacking tips through the Internet and start hacking your website. All that is needed is doing a search on google with keywords like "how to hack website‖, "hack into a website‖, "Hacking a website‖ etc. The following article is not an effort to teach you website hacking, but it has more to do with raising awareness on some common website hacking methods. The Simple SQL Injection Hack SQL Injection involves entering SQL code into web forms, eg. login fields, or into the browser address field, to access and manipulate the database behind the site, system or application. When you enter text in the Username and Password fields of a login screen, the data you input is typically inserted into an SQL command. This command checks the data against the relevant table in the database. If you‘re input matches table/row data, you're granted access (in the case of a login screen). If not, you're knocked back out. In its simplest form, this is how the SQL Injection works. It's impossible to explain this without reverting to code for just a moment.Here is the code Suppose we enter the following string in a User name field: ' OR 1=1
The authorization SQL query that is run by the server, the
37
command which must be satisfied to allow access, will be something along the lines of: SELECT * FROM users WHERE username = „USRTEXT ' AND password = „PASSTEXT‟ Where USRTEXT and PASSTEXT are what the user enters in the login fields of the web form. So entering `OR 1=1 — as your username, could result in the following actually being run: SELECT * FROM users WHERE username = ‗' OR 1=1 — 'AND password = '‘
Here is The example In terms of login bypass via Injection, the hoary old ' OR 1=1 is just one option. If a hacker thinks a site is vulnerable, there are cheat-sheets all over the web for login strings which can gain access to weak systems. Here are a couple more common strings
38
which are used to dupe SQL validation routines: username field examples:
admin'—
') or ('a'='a
”) or ("a”=”a
hi” or "a”=”a
Cross site scripting ( XSS ): Cross-site scripting or XSS is a threat to a website's security. It is the most common and popular hacking a website to gain access information from a user on a website. There are hackers with malicious objectives that utilize this to attack certain websites on the Internet. But mostly good hackers do this to find security holes for websites and help them find solutions. Cross-site scripting is a security loophole on a website that is hard to detect and stop, making the site vulnerable to attacks from malicious hackers. This security threat leaves the site and its users open to identity theft, financial theft and data theft. It would be advantageous for website owners to understand how cross-site scripting works and how it can affect them and their users so they could place the necessary security systems to block cross-site scripting on their website.
Denial of service ( Ddos attack ): A denial of service attack (DOS) is an attack through which a person can render a system unusable or slow down the system for legitimate users by overloading the resources, so that no one can access it.this is not actually hacking a webite but it is used to take down a website. If an attacker is unable to gain access to a machine, the attacker
39
most probably will just crash the machine to accomplish a denial of service attack,this one of the most used method for website hacking I recently wrote an article on www.ethicalhacking.do.am on Denial Service
Cookie Poisoning: Well, for a starters i can begin with saying that Cookie Poisoning is alot like SQL Injection Both have 'OR'1'='1 or maybe '1'='1' But in cookie poisoning you begin with alerting your cookies Javascript:alert(document.cookie) Then you will perharps see "username=rahul" and "password=hacking123" in this case the cookie poisoning could be: Javascript:void(document.cookie="username='OR'1'='1"); void(document.cookie="password='OR'1'='1"); It is also many versions of this kind... like for example ' '1'='1' 'OR'1'='1
40
'OR'1'='1'OR' and so on... Password Cracking
Hashed strings can often be deciphered through 'brute forcing'. Bad news, eh? Yes, and particularly if your encrypted passwords/usernames are floating around in an unprotected file somewhere, and some Google hacker comes across it. You might think that just because your password now looks something like XWE42GH64223JHTF6533H in one of those files, it means that it can't be cracked? Wrong. Tools are freely available which will decipher a certain proportion of hashed and similarly encoded passwords.
Comments