<node id="682009">
  <nid>682009</nid>
  <type>news</type>
  <uid>
    <user id="34541"><![CDATA[34541]]></user>
  </uid>
  <created>1745516053</created>
  <changed>1745516237</changed>
  <title><![CDATA[Spy vs. Spy: A New Automated Removal Tool Can Stop Most Remote-Controlled Malware]]></title>
  <body><![CDATA[<p><a href="https://www.the-independent.com/tech/botnet-cyber-attack-fbi-wang-b2553696.html">Cyberattacks</a> can snare workflows, put vulnerable client information at risk, and cost corporations and governments millions of dollars. A botnet — a network infected by malware — can be particularly catastrophic. A new Georgia Tech tool automates the malware removal process, saving engineers hours of work and companies money.&nbsp;</p><p>The tool, ECHO, turns malware against itself by exploiting its built-in update mechanisms and preventing botnets from rebuilding. ECHO is 75% effective at removing botnets. Removing malware used to take days or weeks to fix, but can now be resolved in a few minutes. Once a security team realizes their system is compromised, they can now deploy ECHO, which works fast enough to prevent the botnet from taking down an entire network.</p><p>“Understanding the behavior of the malware is usually very hard with little reward for the engineer, so we’ve made an automatic solution,” said <a href="https://runzezhang1995.github.io/">Runze Zhang</a>, a Ph.D. student in the <a href="https://scp.cc.gatech.edu/">School of Cybersecurity and Privacy</a> (SCP) and the <a href="https://ece.gatech.edu/">School of Electrical and Computer Engineering</a>.&nbsp;</p><p>The researchers presented the paper, “<a href="https://www.ndss-symposium.org/ndss-paper/hitchhiking-vaccine-enhancing-botnet-remediation-with-remote-code-deployment-reuse/">Hitchhiking Vaccine: Enhancing Botnet Remediation With Remote Code Deployment Reuse</a>,”&nbsp;at February’s <a href="https://www.ndss-symposium.org/">Network and Distributed System Security &nbsp;(NDSS) Symposium</a>. ECHO’s<a href="https://github.com/CyFI-Lab-Public/ECHO"> open-source code</a> is available online.</p><p><strong>Botnet Backstory</strong></p><p>Botnets have been a problem since the 1980s and have grown in potency recently. In 2019, for example, a vicious malware called Retadup <a href="https://decoded.avast.io/janvojtesek/putting-an-end-to-retadup-a-malicious-worm-that-infected-hundreds-of-thousands/">compromised</a> Windows systems throughout Latin America. A Czech cybersecurity company, Avast, partnered with the French government to take down this bot. They reverse-engineered the malware, effectively creating a “vaccine” for it in the process. As effective as that solution was, it wasn’t easily replicable.</p><p><a href="https://saltaformaggio.ece.gatech.edu/">Brendan Saltaformaggio</a> saw an opportunity, though.&nbsp;</p><p>“This is a really good approach, but it was extremely labor-intensive,” said Saltaformaggio, an associate professor in SCP. “So, my group got together and realized we have the research to make this a scientific, systematic, reproducible technique, rather than a one-off, human-driven, miserable effort.”</p><p><strong>Botnet Breakdown</strong></p><p>ECHO eradicates malware in three stages. First, it determines how the malware deploys its malicious code. Then, ECHO identifies the capabilities of this deployment mechanism and discovers how they can be repurposed for remediation. Next, it builds a remediation code that leverages these same mechanisms to disable the malware. That code is then tested and eventually pushed out to the system. The team tested ECHO on 702 Android malware samples and successfully stopped malware in 523 of them.&nbsp;</p><p>They hope ECHO’s success will halt attackers in their tracks.&nbsp;</p><p>“A way we approach problems in our lab is to find the tradeoff between the attackers’ effort versus our effort to fight them,” Saltaformaggio said. “We can never achieve a perfect solution, but we can raise the bar high enough for an attacker that it wouldn't be worth it for them to use malware this way.”</p><p>With tools like ECHO, botnets can be removed before they cause economic and operational damage. Malware is ever-evolving, but Saltaformaggio and his team are improving their methods along with it. The next malware attack is imminent — but so is the solution.&nbsp;</p><p><em>Funding from the Office of Naval Research, the Defense Advanced Research Projects Agency, and the National Science Foundation.</em></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2025-04-24T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[This cybersecurity innovation from Georgia Tech turns malware against itself. ]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p><strong>This cybersecurity innovation from Georgia Tech turns malware against itself.&nbsp;</strong></p>]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="676931">
            <nid>676931</nid>
            <type>image</type>
            <title><![CDATA[Runze.jpg]]></title>
            <body><![CDATA[<p>Runze Zhang presents at NDSS.</p>]]></body>
                          <field_image>
                <item>
                  <fid>260782</fid>
                  <filename><![CDATA[Runze.jpg]]></filename>
                  <filepath><![CDATA[/sites/default/files/2025/04/24/Runze_0.jpg]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/2025/04/24/Runze_0.jpg]]></file_full_path>
                  <filemime>image/jpeg</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[Runze Zhang]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<p>Tess Malone, Senior Research Writer/Editor</p><p>tess.malone@gatech.edu</p>]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>1214</item>
          <item>1188</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Computer Science/Information Technology and Security]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>153</tid>
        <value><![CDATA[Computer Science/Information Technology and Security]]></value>
      </item>
      </field_categories>
  <core_research_areas>
          <term tid="145171"><![CDATA[Cybersecurity]]></term>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>1214</item>
          <item>1188</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[News Room]]></item>
          <item><![CDATA[Research Horizons]]></item>
      </og_groups_both>
  <field_keywords>
          <item>
        <tid>187915</tid>
        <value><![CDATA[go-researchnews]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
