Angler exploit kit generated by "admedia" gates

Published: 2016-02-18
Last Updated: 2016-02-18 00:44:29 UTC
by Brad Duncan (Version: 1)
5 comment(s)


On 2016-02-01, the Sucuri blog reported a spike in compromised WordPress sites generating hidden iframes with malicious URLs [1].  By 2016-02-02, I started seeing exploit kit (EK) traffic related to this campaign [2].  Sucuri noted that "admedia" was a common string used in malicious URLs generated by these iframes.  Because of that, some people (including me) use the term "admedia" when referring to traffic generated by this campaign.  These "admedia" URLs act as a gate between the compromised website and the EK server.  EK traffic associated with this campaign has generally sent TeslaCrypt ransomware.  However, characteristics of this campaign have evolved since Sucuri's original blog post.

  • Since 2016-02-11, I've usually seen the term "megaadvertize" used in these gate URLs instead of "admedia" [3, 4, 5].
  • Although we first saw Nuclear EK from this campaign, during the past week or so, these admedia gates have led to Angler EK.
  • In the past 24 hours, I saw a Joomla site generate an admedia gate, so this campaign is no longer limited to WordPress sites.

Other sites like the Malwarebytes blog have also documented this campaign [6].  Sites like Malwarebytes and DeepEnd Research have also documented most of these recent changes [7, 8].  Let's look at a recent Angler EK infection related to this "admedia" campaign.  In today's example, the chain of events starts with a compromised Joomla site.

Shown above:  HTML from the compromised site that kicked off this chain of events.

Today's infection

On Wednesday 2016-02-17 at approximately 18:14 UTC, I got a full chain of events.  The chain started with a compromised website that generated an admedia gate.  The gate led to Angler EK.  Finally, Angler EK delivered TeslaCrypt, and we saw some callback traffic from the malware.

  • - - admedia gate
  • - - Angler EK
  • - - TeslaCrypt callback traffic

Shown above:  A pcap of the infection traffic filtered in Wireshark.

Shown above:  Some of the events generated by reading the pcap in Snort using the Talos subscription ruleset.

Shown above:  Some of the events generated in Sguil by using tcpreplay in Security Onion with Suricata and the EmergingThreats Pro ruleset.

Shown above:  The infected Windows desktop after Angler EK delivered TeslaCrypt.


How did the compromised website generate the admedia gate?  It was caused by injected script.  As the Sucuri blog already reported, each .js file returned by the compromised site had malicious script appended to it.  In a case on 2016-02-15, I also saw the same type of script included in an HTML page from the compromised website [5]; however, today's traffic only shows injected script in the .js files.

Shown above:  Example of malicious script appended to .js files sent by the compromised web server (1 of 3).

Shown above:  Example of malicious script appended to .js files sent by the compromised web server (2 of 3).

Shown above:  Example of malicious script appended to .js files sent by the compromised web server (3 of 3).

Each example of injected script has a long string of hexadecimal code.  Translate that string from hex to ASCII, and you'll find a URL for the admedia gate.

Shown above:  The ASCII translation of that long hex string.  The admedia gate is highlighted in yellow.

In the traffic, an HTTP GET request to the admedia gate is followed by an HTTP POST.  The HTTP POST returns more obfuscated script.  That script generates a URL for an Angler EK landing page.  How can we check this?  Notice the "eval" function highlighted in the image below of HTML text returned by the admedia gate.

Shown above:  HTML and javascript returned by the admedia gate.

Take that HTML text and put it in a text editor.  Change the "eval" to "alert" and save that text to a separate HTML file.

Shown above:  Changing the "eval" to "alert" and saving the text in a separate HTML file.

Open your newly-saved HTML file in a browser, and you should see the Angler EK landing page URL appear in a pop-up alert.

Shown above:  The Angler EK landing page URL in a pop-up alert.

Below are images of the Angler EK traffic from today's infection.

Shown above:  HTTP request for the Angler EK landing page.

Shown above:  HTTP request for the Angler EK Flash exploit.

Shown above:  HTTP request for the Angler EK malware payload.

Final words

So far, I've only seen TeslaCrypt from this admedia campaign.  In fact, I've seen a whole lot of TeslaCrypt lately, with little other ransomware from EK traffic.  For example, I last saw CryptoWall on 2016-02-05 [9].  Since then, I haven't noticed any CryptoWall.

However, my field of view is currently limited, and there's plenty of information on other types of ransomware that's been making the rounds lately [10, 11, and 12 to name a few].

Have you seen any admedia Angler EK or similar activity?  If so let us know in the comments section below.

Traffic and malware for this ISC diary can be found here.

Brad Duncan
Security Researcher at Rackspace
Blog: - Twitter: @malware_traffic



5 comment(s)


Excellent write up Brad! We observed the same traffic-type as well today. Two admedia gate to Teslacrypt and one of them was to the same site you mentioned: summerspellman[.]com.

Appreciate the references and caps. These diary entries end up as exercises for our team --and me!

Thanks for the kind words. Always nice to hear from others who are seeing the same indicators.

- Brad
Great analysis! Couple days ago we got hit with the same malware through almost the exact same sequence of events. The malware held a lot of files hostage, but it was quickly contained and there was no lasting damage. Thank goodness for backups! Check out this malwr analysis.
This is some nasty stuff.

here are a couple of additional domain names used for the same purpose:

Basically they mean "colored face" in Russian, hinting that these are probably frontends, i.e. "belayamorda" means "whiteface" in English, etc.
Thanks for the additional domains! @Chris, yeah, it's some nasty stuff, alright.

Diary Archives