<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Analysis on Polaris64&#39;s blog</title>
    <link>https://blog.polaris64.net/tags/analysis/</link>
    <description>Recent content in Analysis on Polaris64&#39;s blog</description>
    <generator>Hugo</generator>
    <language>en-uk</language>
    <lastBuildDate>Mon, 24 Aug 2020 12:34:40 +0100</lastBuildDate>
    <atom:link href="https://blog.polaris64.net/tags/analysis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WordPress Hacks: jQuery JS script injection</title>
      <link>https://blog.polaris64.net/post/wordpress-hacks-jquery-js-script-injection/</link>
      <pubDate>Mon, 06 Mar 2017 22:04:00 +0000</pubDate>
      <guid>https://blog.polaris64.net/post/wordpress-hacks-jquery-js-script-injection/</guid>
      <description>Introduction In the second of my series of articles about different exploits seen for WordPress sites, I discuss a particular attack that causes all pages on an infected site to redirect to a page of the attacker&amp;rsquo;s choice, which in this case was an affiliate link. This attack involves adding malicious code to jQuery .js files based on the assumption that jQuery is probably going to be included in every page request.</description>
    </item>
    <item>
      <title>WordPress Hacks: functions.php Backdoors</title>
      <link>https://blog.polaris64.net/post/wordpress-hacks-functions-php-backdoors/</link>
      <pubDate>Fri, 03 Mar 2017 22:03:00 +0000</pubDate>
      <guid>https://blog.polaris64.net/post/wordpress-hacks-functions-php-backdoors/</guid>
      <description>Introduction I recently noticed that a number of our client sites had some suspicious code added to the top of the functions.php file for each of the installed themes. This is an investigation into this code and details of how to remove it.&#xA;I am making this information available in the hope that it will be a useful resource for anybody that suffers this attack on their own WordPress sites. I strongly believe that by making this information public I can help others to combat these types of attacks.</description>
    </item>
  </channel>
</rss>
