<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Uptick in Solarwinds exploit domain flagging in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/uptick-in-solarwinds-exploit-domain-flagging/m-p/482362#M1601</link>
    <description>&lt;P&gt;Starting early Saturday morning (4/23) we started getting a large number of DNS threat alerts for 3 domains associated with the Solarwinds exploit. These domains are now resolving to multiple Leaseweb IPs (as I recall, they were NX previously). Digging thru the Threat &amp;amp; Vulnerability database, these 3 domains are still flagged, but the other domains associated with the compromise are no longer active in the database. Checking packet dumps, I am seeing many DNS queries for these other domains resolving to the same Leaseweb IPs as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is anyone aware of recent changes to these exploit domains? Shouldn't all the domains still be in the threat database?&lt;/P&gt;</description>
    <pubDate>Mon, 25 Apr 2022 17:44:23 GMT</pubDate>
    <dc:creator>Adrian_Jensen</dc:creator>
    <dc:date>2022-04-25T17:44:23Z</dc:date>
    <item>
      <title>Uptick in Solarwinds exploit domain flagging</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/uptick-in-solarwinds-exploit-domain-flagging/m-p/482362#M1601</link>
      <description>&lt;P&gt;Starting early Saturday morning (4/23) we started getting a large number of DNS threat alerts for 3 domains associated with the Solarwinds exploit. These domains are now resolving to multiple Leaseweb IPs (as I recall, they were NX previously). Digging thru the Threat &amp;amp; Vulnerability database, these 3 domains are still flagged, but the other domains associated with the compromise are no longer active in the database. Checking packet dumps, I am seeing many DNS queries for these other domains resolving to the same Leaseweb IPs as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is anyone aware of recent changes to these exploit domains? Shouldn't all the domains still be in the threat database?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 17:44:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/uptick-in-solarwinds-exploit-domain-flagging/m-p/482362#M1601</guid>
      <dc:creator>Adrian_Jensen</dc:creator>
      <dc:date>2022-04-25T17:44:23Z</dc:date>
    </item>
  </channel>
</rss>

