How It Works
1.What is PopLaunch?
If you have seen the following quote you have seen PopLaunch.
c 1999,2000 PopLaunch all rights reserved. The FIRST encrypted Launch
Hosting by M@sTer@GeNTs. Attempting to infringe upon the copyrights of
PopLaunch or attempting to harm the natural course of business of PopLaunch
users will be subject to SEVERE civil and/or criminal penalties
(including but not limited to attempting to hack and/or broadcast the
location of client sites).
ALL clients not honoring remove requests will be terminated (Call
1-800-804-4352 alternatively or for assistance with the PopLaunch browser).
PopLaunch is a spamming system that is usually sent out one of two ways. Through relay rape of a server or through a spam friendly provider. The system was designed to provide anonymity as to the source of the e-mail and the location of the website for the clients. Clicking on the link in the message will send your browser on a trip to
three web pages. The service uses Java Script, redirects, encoded scripts and URLs, daughter windows with no address bar, all to hide the location of these sites. The final
web page will be that of the PopLaunch client.
2. How does PopLaunch work?
The Simple Explanation
The spam is sent in HTML format containing Java Script. Most of what appear to be URLs in the source code are fake. The use of the word f"zero"rm is used instead of the proper f"o"rm to make all form actions in the message invalid.
There is only one valid and active link in the spam. Clicking on this link will begin the process.
The chain of webpages begins with a stop at www.angelfire.com, followed by a second
stop at a redirecting site and finally the site where the spam advertised. Over the course of these stops, the following things will occur.
The right mouse button will be disabled, to stop you from seeing the source code of any pages.
Your main browser window will be resized smaller and an ad for Stealthlaunch/PopLaunch will appear in
it or it may just be blank.
A daughter window will open and maximize to cover the entire screen, this window will not have a tool bar or address bar. It will have a new toolbar loaded by Poplaunch that provides limited functionality. The final site will load in this window.
What PopLaunch does is reverse the process that you may have seen when an advertising pop-up window occurs on your screen. This ad will usually be in a daughter window with the main site in your browser window. PopLaunch puts the ad in the main window and the site in the daughter window.
The Complex Answer.
For those who really want to know how this is accomplished, here are the details.
The information below refers to a spam decoded by Spamless and posted to
News.admin.net-abuse.email on 2/11/00. Reposted here with his permission. The Angelfire
page is no longer active, but the ones controlled by ETC could be.
There have been some changes.
First, the name servers
(getting to the first page)
The obfuscated URL is in the second level domain jjjjjjjj.com.
The name server sends you to another host.
USUALLY it is angelfire.com (doing a traceroute would
then show angelfire.com and you could complain to them).
It may be that the angelfire.com page is now down and
they have changed the CNAME (see below) to their
SO CURRENTLY the name servers give an alias which is on their
Apparently they have been having problems.
Now they have put their first page up on their OWN system.
Apparently, of the four servers they have up at the IP addresses
22.214.171.124x where x=1,2,3,4 ONLY 126.96.36.199 is actually up.
So, they have to run EVERYTHING from that and from 188.8.131.52.
That obfuscated URL is handled by the name servers for the
jjjjjjjj.com second level domain. If you just do a nameserver
lookup for the name servers ("dig jjjjjjjj.com ns") you won't
find any (that will go to the "authoritative" source, the
name servers themselves, and they are configured to lie and
say that "localhost" is the name server). Instead, to find
what name servers actually are used, check at the 'net's
They have four name servers that are used (only the third
is currently alive - that is enough, though)
The name servers used are (check at the root servers for the 'net)
; <<>> DiG 8.2 <<>> @a.root-servers.net jjjjjjjj.com ns
jjjjjjjj.com. NS QC1.QZAA.COM. A 184.108.40.206
jjjjjjjj.com. NS QC2.QZAA.COM. A 220.127.116.11
jjjjjjjj.com. NS QC3.QZAA.COM. A 18.104.22.168
jjjjjjjj.com. NS QC4.QZAA.COM. A 22.214.171.124
Attempting to resolve the obfuscated URL gets me:
NO RESPONSE FROM QC1.QZAA.COM.
NO RESPONSE FROM QC2.QZAA.COM.
CNAME fx1.angel.jjjjjjjj.com from QC3.QZAA.COM.(*)
NO RESPONSE FROM QC4.QZAA.COM.
(*) a CNAME (canonical name) entry is an alias and claims that this
obfuscated URL is just a different name for their other server
fx1.angel.jjjjjjjj.com (usually this is for angelfire.com
where they usually put up the starting page - when that goes
down they can keep the spam run going by putting up the page
with the same directory structure, in this case "/wow/wow/"
on their own server and resetting the entry in their name server).
Finding the IP address for the canonical name (where one goes
to get the first page) gives (no responses except from
fx1.angel.jjjjjjjj.com. A 126.96.36.199
and so one can reach the first page in the chain at:
(NOTE that this is just the QC3.QZAA.COM machine itself).
The First Page:
The first page (usually on angelfire.com, but currently on their own machine
for this run) is designed to hide locations and send you on to the next step
which (currently) is to another web server which sends a REDIRECT (http
header) to the final site.
As the page originally loads one sees:
HTTP/1.1 404 Not Found
Which is interesting. It gives a PAGE NOT FOUND HTTP header.
Then it sends the page! (DON'T TRUST THAT HEADER of course)
There is more ... below this header (values) section there
decrypts and writes more stuff to the page.
What it writes is another encrypted section with decryptor
which writes a final set of stuff to the page.
This sets up a frameset and, depending on your browser goes to one of two
decryption - it used to be that the values, above, that are loaded first,
were used in this - now only "mpage0" is used and that is a null
For IE one has:
flashplugincheck = "/index.cgi?coded=high&classid=";
and the URL is created as:
IE URL: flashplugincheck + classid + codebase + http11 + nav + mpage0
For Navigator one has:
flashplugincheck = "/index.cgi?coded=high&classid=";
and the URL is created as:
NAV URL: flashplugincheck + classid + codebase + http11 + nav + mpage0
The code here is much cleaner than it was a week ago! Not *very* good, for
all those variables set in the first load of the page are ignored (mpage0 is
a null string) but at least it is a lot cleaner than it was.
This results in the following URLS:
Internet Explorer URL:
(these are relative URLs: it used to be that they were absolute URLs to
a different server - but now everything is on just two machines at
two IP addresses)
So, the URLs are:
The REDIRECTING WEB SERVER:
Those URLs do NOT correspond to any pages. Instead, using them goes to the
web server at 188.8.131.52 which responds to those URLs with an
http-redirect header ("302" header).
HTTP/1.1 302 Found <-- it FOUND something to do - a location to give you
(*) those three lines marked with asterisks make up one LONG number.
HTTP/1.1 302 Found
NOTE that there is one LONG junk userid number followed by "@" and
This is a numeric IP address as a dotted octal quad (the bytes making
up the address are in octal).
The first number is 0......00000000100 (starting with 0 is OCTAL).
When parsed by your machine, it should convert this to a number and check
that it is between 0 and 255 (it is much too large, of course) BUT
your machine will probably drop high bits and this is just a few
very high bits plus the octal number 0100_octal=64_decimal. That is
what is seen (it does not see the high bits) and treats it as the
number 64_decimal which IS between 0 and 255.
The next number in the IP address (in both cases) is 0.....204.
Again, this is the octal number 0204_octal=132_decimal plus a few very
high bits (this should be parsed, after having the high bits overflow
away, as the number 132_decimal - a number which IS between 0 and 255).
The next number is 000010=010_octal=8.
The next is 000055=055_octal=45_decimal.
So ... this is at 184.108.40.206 on port 23521.
So, the URLs are:
The LOADING PAGE
These are not the URLs for the pages that you see in your browser.
In fact, for Navigator, we have to go through a few more pages before we
even get to the loading page! (it appears to be a bit more difficult
in Netscape to kill the right mouse click and control key presses).
For Navigator, the URL above leads to:
(the Navigator URL page uses a [SCRIPT] tag with SRC=that_url to load
It is doubly encrypted. It loads, writes the first decrypted version to your
browser and then that decrypts and writes more to the browser. The final
code blocks mouse clicks and keypresses.
This code USED to be run (in prior versions of PopLaunch) for IE and
Navigator, so the first section just determines which browser one is using.
However, this page does not appear to be loaded if one uses IE.
current page with the page from the URL at (it uses a relative URL):
This is a frameset which loads a main page from:
(I have cleaned up the actual URLs in the pages - they have long, junk,
userids and have dotted octal quads with some junk high bits, etc.)
So ... the Navigator URL (from the redirecting web server) loads more
frameset which contains the page at the last URL listed above.
That final page is pretty much exactly what you get from the URL (from the
redirecting web server) sent to IE in one step.
The page (either from the redirecting web server in IE or after loading the
browser. It does two things.
the onUnload command which many sites use to open a new window when you
Unload the current window, that is, leave a page - that is how all those pop
up windows open when you try to leave a site). Those functions are used when
you try to leave But that is for later (when you try to leave).
Second, it sets up a frameset and loads the actual page (yes, FINALLY) that
appears in your browser in the frame.
The page you see
The location of the final page that loads in your browser (FINALLY) is:
(NOTE that only the "&user=#" number value varies and is not
Again, we have a junk userid followed by an "@" and an octal dotted
the IP address and the location for the final page that loads is:
This changes to 657700 in Netscape.
The order form page
On this page you find a link to the signup page. That link is:
again, this is different if you use Netscape.
and if you don't like the junk, the signup page can be reached at:
this changes in Navigator to 657700
This signup page has an order form (give them your credit card!
and the data is sent unencrypted - this is NOT a SSL page!).
This is a "give me your credit card info" form with action:
(NOTE: You have to use the full URLs give above. If you shorten them you might
up at MSN.COM instead!)