Why am I being hacked?
To really know what you're dealing with you have to get inside the head of a script kiddie or a hacker if you want to actually "secure" your systems. Since there are so many factors, many of which that are usually out of the control of most individuals, I'm using the phrase "secure" loosely. From a web or online security standpoint I've worked with several companies over the years, usually in a post-attack analysis, trying to determine what happened, how to recover (if possible) and how to harden against the attack again. Companies often do not spend money on security before an attack and say things like "It's never happened before." or "Why would they target us?" or "No we haven't been hacked." when in actuality they have.
There are several reasons why someone or a group might want to take over a webpage, a blog, a webserver, or a MySQL database server. Here are a few of the reasons I've experienced myself for why someone would exploit a site or page.
Web Real Estate
Mission critical systems that rely on a
database need to be secured. Not only is there the risk of someone
data mining a database of personal data, but there are also risks for the
database server that contains the database and/or the website servers
that host the site receiving or displaying the data. One of the ways
people can cause havoc on a server is by using an SQL Injection Attack.
In November of last year I wrote a post about
SQL Injection Attack Precautions. It talks about who's ultimately responsible in terms of securing a system since usually in most cases the blame for an attack is spread across several people.
How
could web real estate be at risk? If someone looks at a form for a
search, they can assume that it is connected to some sort of database.
Blindly hacking at the form, they will not be able to tell if the
database is a PHP array, an SQL database, or an XML file until they
receive an [un]intended response. Through passing unexpected characters
into the form they can potentially break the form, cause a stack overflow on the server (effectively crashing it),
or break the application that is handling the form. Something like putting a server into an endless loop can bring a server to its digital knees. This usually involves passing escape characters to add extra slashes, closing quotes (single
and double), programming language terminations, or by passing HTML code
into the form. Passing empty form fields can break some forms, while
others can be broken by simply disabling Javascript.
When
a web form is broken it returns valuable information to an attacker
about the structure of the system, the type of server services running,
and the quality of the code on the system itself. In my experience most
websites with easily hackable code are frequented more heavily by
would-be attackers and script kiddies than sites that return no errors
or information to an attacker. Since most modern web servers are
hosted in server farms with high bandwidth connections, to outside
attackers it will more than likely be the same payoff for hacking a
sophisticated site versus a simple site. They both offer the similar bandwidth and server resources and they are usually designed to be managed remotely so there is little chance the Administrator will spot the attack.
If an attacker sees an increased level of security, they're less likely
to attack a server simply because their efforts will be undone much more
quickly or they'll be caught because they will have to try harder.
Web "Street Cred"
Just like the real world, online hackers need notoriety. That being said, there are individuals in the hacking community who love a challenge. Some websites
such as tech blogs, newspapers, social media accounts, video streaming websites and social
networks are going to be more at risk for someone trying to replace
content or services simply to make a name for themselves. There are far
more people looking to become famous from a hacking attempt than there
are people looking to steal information and sell it on some black market. The skill sets required for guessing a password to take over a page vs. actually deriving unencrypted usable data that can be sold are night and day different. There are quite a few apps in the open that will crack or guess a password. There aren't very many individuals that can successfully write a root kit. Sometimes an attacker can simply guess the password to get in and look at the code. The guys who do it for a living will not be bragging about it unless they're making a sales pitch for paying work behind closed doors. You will see script kiddies doing it so they can make a name for themselves (think Anonymous).
Political Reasons
Some "groups" like Anonymous take pride in bringing down sites and exploiting pages and accounts with opposing views or showing companies and corporate conglomerates that they have glaringly open holes in their security. Search for "Anonymous Hacks Burger King Twitter" on Google. While there likely are real hackers that operate under the "Anonymous" moniker, most of the exploits I've seen are pretty amateurish. If Anonymous were really a serious group there would more than likely be now more online trading (or stock market for that matter).
Bad SEO
Some people just want more links for their own sites. These people can be spammers and sometimes they're legitimate businesses that have paid for a service that they themselves weren't quite sure on. In the past there was a practice of spamdexing where a website listed in major directories or topics pertaining to the contents of the site would be picked up and rewarded by the search engines. Fake sites and phishing sites soon caught onto this. The search engines changed their policies, but sometimes in countries throughout the world word doesn't travel so fast through translation. Many "SEO specialists" mention that they can get a site listed through link sharing. This is more than likely how if they are overseas.
An example of spam-dexing from the
Search Engine Journal (3/12/2013)
"There are many sites with spam on their sites that can’t see the links
that they are showing where you couldn’t see unless you went into the
code. Google bot shows that a Top 50 University has “cheap viagra
pills” on their main page."
To find out which one you can search for
University Viagra on Google.
Data Capturing including Credit Cards and Social Security Numbers
Some people are a little more secretive about their exploits and they will hide code on a system to take advantage of web visitors and traffic. This may take the form of database copying or replication (if the site is storing e-mail addresses, credit card numbers, or sensitive data). The attackers may send copies of the real submissions to their own server. They may monitor statistics from the site (for a competitor). Some attackers inject malware into the code so they can infect user computers. In a previous post I talk about the
hacking of clothing manufacturer Calvin Klein and how I started receiving SPAM from the newly created e-mail address I used for them the day I signed up. Calvin Klein of course denied any knowledge of this or interest in rectifying the issue.
Additionally when someone is actually capturing all information to a system on the system itself, any information passed is vulnerable. This includes Social Security Numbers, Credit Card numbers, and anything else that may be submitted (student ID numbers). Depending on the type of site, this is a huge risk to clients, customers, and worse... the brand in terms of PR backlash.
Bot Net
Web servers can be powerful, plentiful machines just ripe for harvesting. Located on massive connections there is very little that can be done to track multiple machines requesting orders from the controlling system (the requests can look like normal web traffic in a packet filter). In numbers, compromised machines can become a powerful collective. Why not run an application in the background on someone else's web server to make it control countless drones while it goes on serving a webpage? This does actually happen. Usually the attacker will install something called a "root kit" which is an app or framework that is undetectable that runs in the background. This allows them to control the server and exploit the bandwidth and resources available to the server. The web page may be up and running and unchanged, so the owner usually won't find out until there is a knock at the door because the machine was used to exploit someone else's, it was controlling countless other machines or worse the website goes down because the ISP pulled the plug at the request of a government or after their own inspection and determination of high traffic. Once a root kit is installed it is easier to use a new machine than it is to clean off the root kit. Without examination the exploit the attacker used may still be in place. It would only be a matter of time before the attack exploited the machine again.
So what are the real risks?
Most of the time the attacks come down to bad password management policies, or use of an unsafe network by someone to log into a website control panel or administration panel (think Starbucks). Every once in a while someone is hit with an XSS attack or a/an [My]SQL injection attack, but this requires someone actually trying to hack the server. Passwords can be captured in open places like airports, coffee shops, hotels, vacation resorts, cruise ships, and on any other unsecured WiFi networks with free applications on the web. Be smart and use strong passwords longer than 10 characters in safe / secure locations and more than likely there will be no issues.
