Difference between revisions of "Hacked MediaWiki"

→ → Go back HOME to Zamboanga: the Portal to the Philippines.
677 bytes added ,  16:15, 3 January 2015
no edit summary
Line 13: Line 13:
Most likely the hacker managed to hack into your site via ftp or cpanel because this type of hacking is not done via user log-in. Spamming via user-login is easy to detect because the wiki keeps a record of every page created with a history. Make sure that you secure you server passwords, cpanel, and ftp passwords.
Most likely the hacker managed to hack into your site via ftp or cpanel because this type of hacking is not done via user log-in. Spamming via user-login is easy to detect because the wiki keeps a record of every page created with a history. Make sure that you secure you server passwords, cpanel, and ftp passwords.


In this case the attack was directed towards the root index.php of the wiki.
In this case the attack was directed towards the root index.php of the wiki.  
|-
 
|
When the index.php is hacked all the pages in the wiki are affected. In other words if you have 250,000 pages in your wiki, all of them are affected. They will show on search results from google with a warning label saying that your site is "hacked"
 
|}
----
{|
|-
|-
|
|
[[File:Hacked.png|212px]]
| The next step is to use your google webmaster tool and fetch the affected page. Once that is done you will see the hidden or cloaked codes within the page. Usually links to other sites for commercial purposes.
The picture to the left shows some of the links that the cloaked codes reveal.
If you do not correct this, the number of visitors to you via search engines will drop to nothing.
|}
|}