This is an old revision of the document!
Script Manual
The program is all based on a simple script engine that we developed on our own which could theoretically be used to submit anything to any platform you can think of. Though it might be a bit hard to figure out the meaning behind the values. This document tries to explain everything in an hopefully easy way.
Here are some helpful links on engine writing and syntax highlighting:
The Structure
Each engine is defined by a simple ini file that has to be placed in the “Engines” folder located in the programs installation folder. To those of you who do not know what a ini file is let me explain it shortly. A ini file is a simple text file that you can open in a text editor like Notepad. It has a section, a variable and a value.
[SECTION] variable=content
Everything is not case sensitive so you don't have to care if you write [SECTION] or [Section]. There are basically two types of engines.
- The once that require an account and login.
You will have to define at least the following sections:
[SETUP], [REGISTER_STEP*], [LOGIN_STEP*], [STEP*] - Those who need no account and no login.
You just need the following sections:
[SETUP], [STEP*]
The SETUP Section
This section defines global settings used to identify a website or set a description. The possible values are described below:
| Variable | Allowed values / Description |
|---|---|
| enabled | 1 = Engine is usable from GUI (default) 0 = Engine is not usable from GUI |
| default checked | 1 = When a new project is created, this engine will be enabled (default) 0 = This engine is not checked on a new project |
| engine type | Name the type of the engine e.g. Directory, Forum, Blog Comment,… This will be used to sort it into the tree view when you edit or create a project. Example: engine type=My Engines |
| description | Just write some notes about this engine that get shown when the user moves the mouse over the engine name in the tree view. You can use \n to generate a line feed. Example: description=My little Engine\n\n© GSA Supported\n\nHave fun |
| dofollow | 1 = This engine creates a do follow link 0 = This engine creates a no follow link 2 = This engines produces both, no follow and do follow links. |
| anchor text | 1 = This engine creates links with your anchor text 0 = This engine creates links with there own anchor texts like “Homepage” or “Visit XYZ's Site”. 2 = This engine might create both, anchor text links and links with there own anchor text. |
| uses pages | 1 = This engine uses pages 0 = This engine uses no pages 2 = This engine uses might use pages or not. For some engines the link will move to page 2 or beyond and might not be visible if you visit that page later. The link is still there but on a different page. This is just an informational data and not used in any way right now. |
| page must have | This parameter is used to check whenever the webpage is usable for this engine or not. The content of this variable has to be present in the webpage (either pure text or html source). The variable can have multiple values separated by a | where just one has to match. Example: page must have1=Powered by XYZ|XYZ Powered page must have2=!not allowed to access this page page must have3=Webpage|Homepage In the above example you see 3 variables and each of them has to match before a engine is used for that website. The ! parameter in “page must have2” means that the following should not appear on the page. |
| url must have | This parameter is used the same way as “page must have” but for the URL string itself and not for the website content. Example: url must have1=/wiki/ url must have2=!wikipedia.com In the above example we will not use this engine for URLs that contain wikipedia.com or do not have “/wiki/” in there URL. |
| fixed url | If no “search term” is used, you have to use this tag to indicate that the submission is just happening on one fixed site (usualy some kind of web 2.0 site with blog creation). Example: fixed url=https://my.opera.com This is than adding the URL to the target URLs of the project and starts a submission to it. |
| search term | This is used to search for new targets on the internet with the help of search engines like google. Example: search term=“Powered by XYZ”|“Powered by XYZ” The example above uses two possible search queries. You can use also encoded the search term already if you want with “%90%AF%24”. This is useful for queries in some strange language. The program will pick one of the queries randomly so the order is not important. |
| add keyword to search | 1 = Add a keyword from the project to the search query 0 = Never add a keyword to the search query 2 = Add just sometimes a keyword to it if it seems to be useful (default) |
| use blog search | 0 = Never use blog search engines 1 = Use blog search engines (default) 2 = Use only blog search engines |
| extract keywords | 1 = Extract keywords from the sites meta tags. These can be used later on 0 = Don't extract keywords (default) |
| extract keywords ignore | Ignores the keywords and will not add them. Example: extract keywords ignore=blog,wordpress If the meta keywords for that site are “SEO, blog, wordpress” then the program will just extract SEO from it. |
| extract urls | 1 = Extract URLs from the sites. 0 = Don't extract URLs (default) If enabled, the program will download verified URLs and try to post to sites found as external links. |
| posted domain check | Overwrites project settings: Avoid posting URL on same domain twice 0 = do not post any link if anything has been posted before 1 = allow to post a link again on the same domain (but only if the URL is different) 2 = special setting for tier projects that would than allow to post several URLs on the same site. |
| skip ext links on | Overwrites project settings: Skip sites with more than 1 = setting from project is applied 0 = setting from project is ignored |
| skip content on | Overwrites project settings: Skip sites where the following words appear 1 = setting from project is applied 0 = setting from project is ignored |
| skip url content on | Overwrites project settings: Skip sites with the following words in URL/Domain 1 = setting from project is applied 0 = setting from project is ignored |
| skip nofollow links on | Overwrites project settings: Try to skip creating Nofollow links 1 = setting from project is applied 0 = setting from project is ignored |
| skip pr on | Overwrites project settings: Skip sites with a PR below 1 = setting from project is applied 0 = setting from project is ignored |
| referrer | Sets a fixed referrer that is used when downloading content or submitting something to this site. Example: referrer=%url% This will always use your URL from the project as a referrer. |
| user agent | Instead of using a user agent that the program chooses for you, you can define it here. Example: user agent=Some Legit Browser v1.01 This might be useful for exploits where you e.g. can send a html link in the “user agent” that is than turned to a real link on a page. |
| extract from email | If you use email verification in the engine you might need to extract not only verification URLs, but also variables like a login or password from the emails. This can be done here. Example: extract from email=key,forum_password=email_pw This example will try to extract the data for key (section key) and forum_password (defined in email_pw section). Please read the chapter Data Extraction for details. |
| whois only | Very special variable that is only used for engines that submit your URL to sites that carry your domain in there URL. 0 = Not a whois only engine (default) 1 = Only whois submission and if not detected as a whois one, skip submission |
| captcha hint | A hint that should be displayed along with the captcha input |
| multiple posts per account | Defines if it is allowed to create more than one post per account. By default this is set to 1 (true) but only used for Article posting engines. On some engines it is useful to set this to 0 (false) when just one Article is possible to be posted (e.g. article in profile link) |
| keep subdomain | Defines if a special domain with it's subdomains should be handled as a new site/domain. Example: keep subdomain=domainXYZ.com If the program has two URLs like A.domainXYZ.com and B.domainXYZ.com, then it will handle them as two different sites where it previously would have taken them as the same. |
| max download size | Overwrites the global filter for the maximum amount of MB to download per GET/POST request. |
The STEP Section
There are 4 types that can be used:
- [REGISTER_STEP*] - used to create an account
- [LOGIN_STEP*] - used to log into the site with the created account
- [STEP*] - he actual submission process
- [EXTRA_STEP*] - an additional submission process
You can define as many steps as you want but they have to be in sequence like [STEP1] [STEP2] and so on.
The following fixed variables can be used:
| Variable | Allowed values / Description |
| find link | Searches the site for a anchor text and downloads that URL to work on with. You can use more than one link text when separated with |. Example: find link=Register|Registrieren|Sign up|Signup The example will search for a link that has at least one of the above anchor texts. |
| find url | Searches the site for a URL that is matching one of the masks defined in the variable. Example: find url=*/register|*/register.php|*/signup/* You should always use find link and find url in combination so that if one fails the other is used. |
| optional find url link | 0 = A link has to be found else we abort the submission (default) 1 = If no link is found we continue to find a form or whatever should be done in the current submission step. Example: optional find url link=0 |
| alternative url | If find url and find link are not finding any URL that can be used, we will generate an alternative URL. Example: alternative url=./register.php\\ |
| browse links | This will take the variable content and browse to the site. It is just useful for directories maybe where you first have to browse to a certain category till you are allowed to start a submission. Example: browse links=%category% If your project category is defined like “Computer :: Software :: Shareware”, than the program tries to surf to Computers followed by finding a link names Software and than Shareware. |
| browse links from root | 1 = The root URL is used for “browse links” in case the start URL is a sublink. 0 = Start the “browse links” from where we are. |
| browse links url mask | Tells the program to just search for URLs matching that mask. |
| just download | 1 = Download the new URL and continue with STEP2 or finish the submission if nothing else should be done. 0 = a form has to be found to start the submission (default) |
| form id | Try to find a form on the current webpage that has a ID as in the variable content. Again you can use | to have multiple variations. Not many sites use a ID in the <form> tag but some do. Example: form id=signupform|signup This tries to find a from with the ID called signupform or singup. |
| form class | Try to find a form on the current webpage that has a class as in the variable content. Again you can use | to have multiple variations. Not many sites use a class in the <form> tag but some do. Example: form class=cls-input This tries to find a from with the class called cls-input. |
| form name | Try to find a form on the current webpage that has a name like the variable content. If no name is used in the <form> tag, the caption of the submit button is used. Example: form name=*Sign Up|*Register This tries to find a form there the name or the submit button's name is either matching “*Sign Up” or “*Register”. |
| form url | Try to find a form where the submission URL would match the variable content. Example: form url=*/signup.php|*/signup/ This tries to find a form where the resulting submission URL after pressing the submit button would match “*/signup.php” or “*/signup/”. |
| form url ignore | Ignores forms where the submission URL would match the variable content. Example: form url ignore=*/search.php This tries to ignore a form where the resulting submission URL after pressing the submit button would match “*/search.php”. |
| form request with | Some Forms get sent by ajax or some other javascript framework and would than need to send a “X-Requested-With” in the html header. By default nothing is sent by in the HTML header. Example: form request with=XMLHttpRequest |
| optional form | 0 = If no form is found we will stop the submission with a failer (default) 1 = the submission process is going on (STEP2 Section e.g.) even if no form has been found. |
| seconds to wait before submission | Will wait a given number of seconds before the form is actually submitted. This is useful to not trigger some robot detection system for some engines. Example: seconds to wait before submission=12 Wait 12 seconds before the form is submitted. |
| seconds to wait before submission condition | This will only delay the submission if something in the variable content is found on the webpage. Example: seconds to wait before submission condition=stop_spam_time If the word “stop_spam_time” is either present in the html source or the visible text we wait with the submission a given time, else we skip this. |
| post data | This is hardly used but will create a custom data that is used to submit to websites instead of using the data from <form>. Example: post data=this=that&something=else Have a look in the Pingback or Trackback engine where this is used. |
| encode post data | 1 = encode the data in a proper way as used in POST protocol 2 = encode it using multipart 0 = take the data as it is without encoding anything 3 = encode it using json syntax |
| variable must be used | A form is only submitted if certain variables have been used in that form. Example: variable must be used=url,login|email The above example requires a form to use the variable “url” or “login” and “email”.\\ |
| add fixed data add fixed data condition remove fixed data remove fixed data condition | This will add a form field if the thing in “add fixed data condition” is found on the webpage. This works only if both variables are defined. Don't worry about this to much as you will probably never use this. It is only required if some sites add data to forms by javascript to prevent automated submissions. You can use “remove fixed data” to just remove that from the posting. Example: add fixed data=code=%captcha%;hidden=0 add fixed data condition=code_sign;hidden_data If the webpage has anywhere the word “code_sign” in it we add a new form field called code that will be filled with a captcha. And if the word “hidden_data” is found we also add a new form field called “hidden” with the content “0”. |
| set unknown variable set unknown variable condition | If a form field is unknown as we didn't define how to fill it in our engine, we could still fill it by something you define here. The submission aborts if this is not defined and something is unable to get filled. The “set unknown variable condition” doesn't have to be used but if it is, the string on that variable must be present to use this. Example: set unknown variable=%question% If a filed is found called “blahantispam193802378” we can still define how to fill this and it gets filled by the value %question% which is handled by a popup asking you how to fill it. Also often used it “set unknown variable=%leave%” which will simply leave the value as it is. |
| match by option label | 1 = A form with a select or radio field is filled by checking the variable content against the option labels (the one you see on the browser). 0 = We will not check for a matching label Example: match by option label=1 |
| match by option value | 1 = A form with a select or radio field is filled by checking the variable content against the option value (hidden from the users eye in browser) 0 = We will not check for a matching value |
| match by prefill | 1 = If the user has filled this field before in the past we use that vontent to fill it (default) 0 = we do not check past submissions on what has been used here.\\ |
| modify submit url modify submit url condition | Sometimes a javascript is modifying the actual submission URL of a form which is not recognized by default. In this case you can do this with the variables. “modify submit url condition” doesn't have to be present. Example: modify submit url=./submit.php?changed=1 modify submit url condition=javascript:modify_url The form URL is changed to “./submit.php?changed=1” if the string “javascript:modify_url” is found on the webpage. |
| modify submit type modify submit type condition | Sometimes a javascript is modifying the actual submission type of a form which is not recognized by default. In this case you can do this with the variables. “modify submit type condition” doesn't have to be present. Example: modify submit type=multipart/form-data modify submit type condition=javascript:modify_type The form URL is changed to “./submit.php?changed=1” if the string “javascript:modify_url” is found on the webpage. |
| remove cookie remove cookie condition | Removes a cookie manually for the given URL/domain Example: remove cookies=%targeturl% This removes any cookie for this domain |
| set cookie set cookie condition | Sometimes cookies are required to submit a form and they are set by javascript so that the program can not detect them. You can do that manually with these variables. “set cookie condition” doesn't have to be present. Example: set cookie=passed_check=1 This sets a cookie named “passed_check” with the value “1”. |
| write file | Writes data to a file. Example: write file=“C:\temp\accounts.txt” “%targeturl%;%login%;%password%” |
| recaptcha sitekey | Get the required recaptcha site key Example: recaptcha sitekey=<fixed key|section|url where to get it> You can either input the sitekey or the url where to extract it or a section from the script how to extract it like: \\recaptcha sitekey=get_key [get_key] type=extract url=/recaptcha.js front=sitekey=“ back=“ |
Variables usable in SETUP and STEP Section
Some variables can be used globally (SETUP) or in the STEP (some only on STEP1) section.
| Variable | Allowed values / Description |
|---|---|
| submit success submit failed captcha failed submit failed retry |