<span id="hs_cos_wrapper_post_body" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_rich_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="rich_text" ><p><span style="font-size: 12.1612px; background-color: transparent;"><img src="https://info.threatstop.com/hubfs/0000_Sec_Logo_with_tm.png" alt="0000_Sec_Logo_with_tm.png" width="320" style="width: 320px; display: block; margin-left: auto; margin-right: auto;"></span></p> <!--more--> <p><span style="font-size: 12.1612px; background-color: transparent;">In February 2017, Palo Alto Networks noted a new take on the “</span><strong style="font-size: 12.1612px; background-color: transparent;">Infy</strong><span style="font-size: 12.1612px; background-color: transparent;">” malware. Redubbing it as “</span><strong style="font-size: 12.1612px; background-color: transparent;">Foudre</strong><span style="font-size: 12.1612px; background-color: transparent;">” (“lightning,” in French) based on the handle of a window used by the keylogger.</span></p> <p>Let's back up a little.</p> <p><a href="https://researchcenter.paloaltonetworks.com/2017/08/unit42-prince-persia-ride-lightning-infy-returns-foudre/">Palo Alto Netoworks</a> sinkholed <strong>Infy</strong> in 2016, but the attackers learned their lesson and <strong>Infy</strong> received upgrades. This new version maintains most of <strong>Infy's</strong> Delphi base. However, it added a few new features in the form of a new keylogger, where <strong>Foudre</strong> gets its name, a new crypto suite, and new de-obfuscation tools. It also is being redirected from <strong>Infy's</strong> sinkhole by the Telecommunication Company of Iran (AS12880). AS12880 first started redirecting traffic aimed at <strong>Infy's</strong> sinkhole and then added in HTTP filtering for their clients in Iran. This means, <strong>Infy</strong> stayed alive in Iran, and <strong>Foudre</strong> is right there with it.</p> <p><strong>Foudre</strong> spreads through <a href="#S-_spearphishing">spear phishing</a> attacks. As with <strong>Infy</strong>, emails targeting select individuals go out as part of the campaign. These emails contain an attachment that executes when clicked. Once running, the dropper downloads a loader, malware DLL, and decoy readme file.</p> <p>When first run, the loader creates an installation folder and copies itself as config.exe to that folder. The DLL determines where the folder is, but seems to be some variant on <strong>%all users%\app data\SnailDriver V&lt;version number&gt;</strong>. After creating the folder, the DLL is also copied to the folder and renamed to something random. The loader then adds itself to the registry to autostart on boot, and after reboot the <strong>rundll32.exe</strong> loads the DLL file, and only if the <strong>lp.ini</strong> file contains a numeric value.</p> <p>It's also notable that <strong>Foudre</strong> checks for itself in memory to avoid reinfecting an already infected system. By scanning for <strong>foudre&lt;trojan version number&gt;</strong> and verifying that the window class is <strong>TNRRDPKE</strong> it can establish if there's been an infection.</p> <p>After infection Foudre tries to steal data like <strong>Infy</strong> did. After infection <strong>Foudre</strong> checks for Internet access by trying to talk to Google. If it receives an <strong>HTTP 200</strong> response ("success") it will attempt to upgrade itself. Regardless of whether the upgrade is successful, the malware installs its keylogger to the system and starts copying the clipboard every ten seconds. In addition, it grabs system info antivirus, browser data, and running processes. Once it gathers the data it determines the current C2 domain using a <a href="https://dochub.threatstop.com/display/TS/D#D-_dga">DGA</a>.</p> <p>After contacting the C2, it determines authenticity by downloading an encrypted signature file. If the cleartext of the file matches a reference file the malware carries with it, then user data sent to the server via HTTP POST requests.</p> <p>Primary targets for the campaign are in Iran, as noted with the redirects, and HTTP filtering. Additional targets have included the United States and Iraq. The targets have not been financial groups, and the filtering by Iranian authorities against the C2 system suggests that this could be targeted at state officials.</p> <p>To enable ThreatSTOP’s protection against <strong>Foudre data</strong> in your firewall turn on the <strong>Foudre DGA domains - Domains</strong> expert target in the ThreatSTOP portal. You Are already protected from <strong>Foudre </strong>if you have the following target enabled in your policy - <strong>Botnet DGAs Tier 1 – Domains </strong>(either standard or expert)</p> <p>If you don’t have a ThreatSTOP account,&nbsp;. <span>If you do have a ThreatSTOP account, instructions to add targets to </span><a href="http://dochub.threatstop.com/display/TS/ThreatSTOP+DNS+Firewall#ThreatSTOPDNSFirewall-DNSFWPolicy">DNS</a><span> or </span><a href="http://dochub.threatstop.com/display/TS/ThreatSTOP+IP+Firewall">IP</a><span> Defense policies are available on the ThreatSTOP Documentation Hub. Or, contact our team.</span></p></span>