Title: 7thwraith's Replies | WordPress.org

---

# 7thwraith

  [  ](https://wordpress.org/support/users/7thwraith/)

 *   [Profile](https://wordpress.org/support/users/7thwraith/)
 *   [Topics Started](https://wordpress.org/support/users/7thwraith/topics/)
 *   [Replies Created](https://wordpress.org/support/users/7thwraith/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/7thwraith/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/7thwraith/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/7thwraith/engagements/)
 *   [Favorites](https://wordpress.org/support/users/7thwraith/favorites/)

 Search replies:

## Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feed does not validate: XML parsing error: <unknown>:137:0: junk after document](https://wordpress.org/support/topic/feed-does-not-validate-xml-parsing-error-ltunknowngt1370-junk-after-document/)
 *  Thread Starter [7thwraith](https://wordpress.org/support/users/7thwraith/)
 * (@7thwraith)
 * [17 years, 1 month ago](https://wordpress.org/support/topic/feed-does-not-validate-xml-parsing-error-ltunknowngt1370-junk-after-document/#post-1033413)
 * > The code is in both your RSS feed and right across your site. The last line
   > of every output file. It does look like a hack but then javascript is not my
   > thing…
 * Thanks esmi! That gave me a clue on how to apply a temporary solution to get 
   rid of the script. Turns out every index.php file in that subdomain was infected
   with that script. So all I did was remove that script.
 * For now, the only thing I’ve done to avoid this from happening again is change
   the FTP password for this account, disable anonymous FTP and disable indexing.
   I’ll keep you guys posted if anything.
 * Thanks everyone!
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feed does not validate: XML parsing error: <unknown>:137:0: junk after document](https://wordpress.org/support/topic/feed-does-not-validate-xml-parsing-error-ltunknowngt1370-junk-after-document/)
 *  Thread Starter [7thwraith](https://wordpress.org/support/users/7thwraith/)
 * (@7thwraith)
 * [17 years, 1 month ago](https://wordpress.org/support/topic/feed-does-not-validate-xml-parsing-error-ltunknowngt1370-junk-after-document/#post-1033204)
 * > Added: The suspicious hacker-like javascript is on your site as well.
 * Where in my site specifically?
 * Thanks again.
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Feed does not validate: XML parsing error: <unknown>:137:0: junk after document](https://wordpress.org/support/topic/feed-does-not-validate-xml-parsing-error-ltunknowngt1370-junk-after-document/)
 *  Thread Starter [7thwraith](https://wordpress.org/support/users/7thwraith/)
 * (@7thwraith)
 * [17 years, 1 month ago](https://wordpress.org/support/topic/feed-does-not-validate-xml-parsing-error-ltunknowngt1370-junk-after-document/#post-1033202)
 * Thanks for the reply. Yes, the last line in the feed validator (the javascript)
   is indeed what’s causing the problem.
 * The thing is, I do not know what file is running this javascript. If anything,
   I’m suspecting two of the plugins, particularly
 * WordPress.com Stats Helper version 0.5.5.3 and WP-Stats-Dashboard version 1.5.4
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Cannot save changes to previous posts and cannot publish new posts](https://wordpress.org/support/topic/cannot-save-changes-to-previous-posts-and-cannot-publish-new-posts/)
 *  Thread Starter [7thwraith](https://wordpress.org/support/users/7thwraith/)
 * (@7thwraith)
 * [17 years, 2 months ago](https://wordpress.org/support/topic/cannot-save-changes-to-previous-posts-and-cannot-publish-new-posts/#post-1009741)
 * Nevermind, prroblem fixed when I tried the repair SQL database tool from my webhost.

Viewing 4 replies - 1 through 4 (of 4 total)