interesting part of the source

[YagerX]

uhm i have a stumbled over this part of the source which will lead to the breaking of the arg if you dont leave it, but hey if we get stuck... ny ways heres the part:

<SCRIPT TYPE="text/javascript">
var gDomain="m.webtrends.com";
var gDcsId="dcs7r34dy000004jxlrao6bqi_1u8z";
var gTrackEvents=1;
var gFpc="WT_FPC";if(document.cookie.indexOf(gFpc+" ;=")==-1){document.write("<SCR"+"IPT TYPE='text/javascript' SRC='"+"http"+(window.location.protocol.i ndexOf('https:')==0?'s':'')+&qu ot;://"+gDomain+"/"+gDcsId+"/wtid.js" ;+"'><\/SCR"+"IPT>");}
</SCRIPT>
<SCRIPT SRC="js/webtrends.js" TYPE="text/javascript"></SCRIPT>
<NOSCRIPT>

notice the m.webtrends part? and it's "ID" dcs7r34dy000004jxlrao6bqi_1u8z?
well all the server sites (1 and 2) have that same id (or possibly account) so if you want to cheat... somehow access that account's info and the arg is yours

[scapermoya]

ive been examining all of the code the whole time (as well as downloading/decompiling the swfs). webtrends is helping them do tracking on this thing. this is advertising after all, but webtrends is just a marketing research company. its nothing to do with the arg.

i suspect if they hide anything in the code of the page, it will be commented.

[Van Helsing]

Lockedzorz