2016-05-26 - ANGLER EK SENDS UPDATED VERSION OF CRYPTXXX RANSOMWARE

NOTICE:

ASSOCIATED FILES:

  • 2016-05-26-Afraidgate-Angler-EK-sends-CryptXXX-ransomware.pcap   (1,101,070 bytes)
  • 2016-05-26-pseudoDarkleech-Angler-EK-sends-CryptXXX-ransomware.pcap   (1,115,419 bytes)
  • 2016-05-26-Afraidgate-Angler-EK-CryptXXX-ransomware-decrypt-instructions.bmp   (3,686,454 bytes)
  • 2016-05-26-Afraidgate-Angler-EK-CryptXXX-ransomware-decrypt-instructions.html   (5,715 bytes)
  • 2016-05-26-Afraidgate-Angler-EK-CryptXXX-ransomware-decrypt-instructions.txt   (987 bytes)
  • 2016-05-26-Afraidgate-Angler-EK-landing-page.txt   (102,905 bytes)
  • 2016-05-26-Afraidgate-Angler-EK-payload-CryptXXX-ransomware.dll   (176,128 bytes)
  • 2016-05-26-Angler-EK-flash-exploit-vs-flash-21.0.0.213.swf   (67,386 bytes)
  • 2016-05-26-page-from-brookslake_com-with-injected-pseudoDarkleech-script.txt   (52,364 bytes)
  • 2016-05-26-pseudoDarkleech-Angler-EK-CryptXXX-ransomware-decrypt-instructions.bmp   (3,686,454 bytes)
  • 2016-05-26-pseudoDarkleech-Angler-EK-CryptXXX-ransomware-decrypt-instructions.html   (5,715 bytes)
  • 2016-05-26-pseudoDarkleech-Angler-EK-CryptXXX-ransomware-decrypt-instructions.txt   (990 bytes)
  • 2016-05-26-pseudoDarkleech-Angler-EK-landing-page.txt   (102,831 bytes)
  • 2016-05-26-pseudoDarkleech-Angler-EK-payload-CryptXXX-ransomware.dll   (176,128 bytes)

NOTES:


Shown above:  Example of a user's AppData\Local\Temp folder when Angler EK sends CryptXXX.

 

TRAFFIC


Shown above:  Traffic from the Afraidgate Angler EK filtered in Wireshark using the filter: http.request or (tcp.port eq 443 and tcp.flags eq 0x0002).


Shown above:  Traffic from the pseudoDarkleech Angler EK filtered in Wireshark using the filter: http.request or (tcp.port eq 443 and tcp.flags eq 0x0002).

ASSOCIATED DOMAINS:

 

IMAGES


Shown above:  Lock screen when the CryptXXX ransomware infection kicks in.

 


Shown above:  HTML file to get to the decryption instructions.

 


Shown above:  Windows desktop when it was rebooted.

 


Shown above:  Going to the site to pay the ransom, you'll have to enter your code.

 


Shown above:  Decryption instructions (part 1 of 3).

 


Shown above:  Decryption instructions (part 2 of 3).

 


Shown above:  Decryption instructions (part 3 of 3).

 


Shown above:  Talos subscriber set signatures still cover callback traffic from the new CryptXXX ransomware.

 


Shown above:  ET PRO signatures also still cover callback traffic.

NOTE: I removed the identification code from the post-infection traffic in my pcaps.  Because of that, I haven't been able to get any of the pcaps to trigger the above ETPRO alerts when using tcpreplay on Security Onion (with Suricata and the ETPRO ruleset).  The above image shows CryptXXX ransomware alerts from post-infection traffic before I sanitized the pcap.

 

Click here to return to the main page.