Timeline for Solving corruption in a .htaccess flle
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2017 at 4:02 | answer | added | Chaoley | timeline score: 1 | |
| Sep 21, 2017 at 12:37 | comment | added | MrWhite |
Curious that the only relevant results in Google for help-insideit.php relate to two hacked sites from two years ago - also on GoDaddy! (Although the actual filename may be insignificant here, hence only two results.)
|
|
| Sep 21, 2017 at 11:02 | comment | added | Simon Hayter | You need to address how they got in... otherwise it'll just happen again and again. Time to check all logs. | |
| Sep 21, 2017 at 10:44 | history | tweeted | twitter.com/StackWebmasters/status/910816940154851328 | ||
| Sep 21, 2017 at 6:58 | comment | added | dan♦ | You should also change your passwords for your account access, FTP, and SSH... See the bottom of their help guide here: Lock down a compromised account. | |
| Sep 21, 2017 at 6:54 | comment | added | dan♦ |
It's not so much "corrupt" as it is "hijacked". You've likely got a PHP file named help-insideit.php somewhere in your directories (maybe several), and this .htaccess file is rewriting requests (visits) from Google, Yahoo, MSN, etc... to that file. They're likely trying to redirect traffic from your site to theirs. I'd suggest working with GoDaddy's hosting support department for help locating and removing those PHP file(s) and resetting the .htaccess file to what you previously had (or just empty it if nothing was in there before).
|
|
| Sep 21, 2017 at 6:45 | history | edited | dan♦ | CC BY-SA 3.0 |
Removed unnecessary closing and modified tag.
|
| Sep 21, 2017 at 6:42 | review | First posts | |||
| Sep 21, 2017 at 6:43 | |||||
| Sep 21, 2017 at 6:37 | history | asked | Howard Meiseles | CC BY-SA 3.0 |