.: GoodLuck 3.0 :.
Released 14 years, 5 months ago. May 2007By SSOPE
- Coded by: SSOPE
- Version: GoodLuck 3.0
- Released date: May 2007, 14 years, 5 months ago.
- Family: GoodLuck
- Category: Remote Access
Server: size: 203,776 bytes tested on Windows XP May 22, 2007
Client to Server Functions:: -Send and receive messages -Engage in a two way chat -Raise "Format Drive" window -Receive Total and Available RAM -Obliterate any running executable -Print designated text -Minimize all windows -Overflow cmd.exe -Receive server executable up time -Empty recycle bin -Send 'heaps of beeps' -Open designated web page -Hide / Show icons -Hide / Show task bar -Black out / Show screen -Open / Close tray -Make icons dance / Stop dance -Disable / Enable shut down -Disable / Enable clipboard -Turn on strobe light/ Turn off strobe light -Caps On / Off -Hide / Show system tray -Hide / Show start menu -Hide / Show clock -Log off XP / OS -Shut down XP / OS -Restart from XP / OS -Type and save designated text in notepad -Commence default screen saver -Set designated clipboard text -Add designated text to Control Panel -Remove text from Control Panel -Have Microsoft's animated character Merlin speak designated text -Raise the checkdisk executable -Close the server executable -Full blown key logger -Receive OS/XP computer name -Receive OS/XP user name -Receive computer up time -Receive OS type and version -Receive clipboard text -Receive all running executables Success from Beta:: +Overview:: - - > The extensive beta testing proved GoodLuck 3.0 to be the same distinguished limitless Trojan that it was expected to be. +Connection Center:: - - > Local connection was always successful. - - >Remote connection was successful in cases where the server was not behind a router. - - > Scanning ports was successful. +Control Center:: - - > Every single option was always successful to its fullest extent once connected. +Key Log Center:: - - > The Key Logger, as well as other Key Log options, were always successful to their fullest extent once connected. +Extras Center:: - - > Every single option was always successful to its fullest extent once connected. Common Errors from Beta:: +"Address in use" - - > Type: Server - - > Reason for Error: The server has been opened twice. +"No room to buffer" - - > Type: Server [and/or] Client - - > Reason for Error: There was not enough available RAM to start or continue a specific winsock function / sequence of events. - - >Solution: Close some programs to clear up RAM and CPU usage, then reopen . +"Wrong state for connection" - - > Type: Server -- > Reason for Error: This error is very rare and only occurs when the server or client closed very abruptly and did not get the chance to communicate it's close and disconnection to it's other half. +"Connection is forcefully rejected" - - > Type: Client -- > Reason for Error: There is only one reported case of this error and it occurred after attempting to scan ports from client to server . +[Discolored Server Interface] -- >Type: Server - -> Reason for Occurrence: The emulation of "Microsoft's Windows Send Error Report" was not adjusted to system default colors and was instead compiled to designated palette colors . +[Connecting to a Server Behind a Router] - - > Type: Server - - > Reason for Occurrence: The server does not auto-forward ports. -- >Solution: Forward server's ports manually. (suggestion: VNC)
URL's and mails were automatically redacted (filtered) for reader's safety. However the filter is not perfect and can't find all harmful elements. If you find something dangerous including file link, website, mail address, profanity... contact me immediately at firstname.lastname@example.org, thank you in advance.