### Install Application Source Files Source: https://github.com/doge-1satellite/ttt2/blob/main/Install/ReadMe.txt Details the main application source file and project file for the Install Win32 application. ```cpp Install.cpp This is the main application source file. Install.dsp This file (the project file) contains information at the project level and is used to build a single project or subproject. Other users can share the project (.dsp) file, but they should export the makefiles locally. ``` -------------------------------- ### Standard Application Files Source: https://github.com/doge-1satellite/ttt2/blob/main/Install/ReadMe.txt Describes the standard precompiled header files used in the Install application. ```cpp StdAfx.h, StdAfx.cpp These files are used to build a precompiled header (PCH) file named Install.pch and a precompiled types file named StdAfx.obj. ``` -------------------------------- ### Gaode Map Basic Setup and Controls Source: https://github.com/doge-1satellite/ttt2/blob/main/Bin/Plugins/Gaode.html This snippet shows how to initialize a Gaode Map with specified center coordinates and zoom level. It also demonstrates how to add various map controls such as ToolBar, Scale, Overview, and a LayerSwitcher using AMap.plugin and AMapUI. ```javascript function getParam(paramName) { paramValue = "", isFound = !1; if (this.location.search.indexOf("?") == 0 && this.location.search.indexOf("=") > 1) { arrSource = unescape(this.location.search).substring(1, this.location.search.length).split("&"), i = 0; while (i < arrSource.length && !isFound) arrSource[i].indexOf("=") > 0 && arrSource[i].split("=")[0].toLowerCase() == paramName.toLowerCase() && (paramValue = arrSource[i].split("=")[1], isFound = !0), i++ } return paramValue == "" && (paramValue = null), paramValue } var lnglat = new AMap.LngLat(getParam("lng"),getParam("lat")); var map = new AMap.Map('container', { resizeEnable:true, zoom:13, center:lnglat }); var mark = new AMap.Marker({ map:map, position:lnglat }); AMap.plugin(['AMap.ToolBar','AMap.Scale','AMap.OverView'], function(){ map.addControl(new AMap.ToolBar()); map.addControl(new AMap.Scale()); map.addControl(new AMap.OverView()); }); AMapUI.loadUI(['control/BasicControl'], function(BasicControl){ map.addControl(new BasicControl.LayerSwitcher()); }); ``` -------------------------------- ### Gaode Map Basic Setup and Controls Source: https://github.com/doge-1satellite/ttt2/blob/main/Client/res/Html/Gaode.html This snippet shows how to initialize a Gaode Map with specified center coordinates and zoom level. It also demonstrates how to add various map controls such as ToolBar, Scale, Overview, and a LayerSwitcher using AMap.plugin and AMapUI. ```javascript function getParam(paramName) { paramValue = "", isFound = !1; if (this.location.search.indexOf("?") == 0 && this.location.search.indexOf("=") > 1) { arrSource = unescape(this.location.search).substring(1, this.location.search.length).split("&"), i = 0; while (i < arrSource.length && !isFound) arrSource[i].indexOf("=") > 0 && arrSource[i].split("=")[0].toLowerCase() == paramName.toLowerCase() && (paramValue = arrSource[i].split("=")[1], isFound = !0), i++ } return paramValue == "" && (paramValue = null), paramValue } var lnglat = new AMap.LngLat(getParam("lng"),getParam("lat")); var map = new AMap.Map('container', { resizeEnable:true, zoom:13, center:lnglat }); var mark = new AMap.Marker({ map:map, position:lnglat }); AMap.plugin(['AMap.ToolBar','AMap.Scale','AMap.OverView'], function(){ map.addControl(new AMap.ToolBar()); map.addControl(new AMap.Scale()); map.addControl(new AMap.OverView()); }); AMapUI.loadUI(['control/BasicControl'], function(BasicControl){ map.addControl(new BasicControl.LayerSwitcher()); }); ``` -------------------------------- ### Server.dsp - Project File Source: https://github.com/doge-1satellite/ttt2/blob/main/Server/ReadMe.txt The Server.dsp file is the project file used by AppWizard to build the Server DLL. It contains project-level information and is used to compile and link the project. This file can be shared among users, but they should export makefiles locally for their build environments. ```dsp # Microsoft Developer Studio Project File - Name="Server" #----------------------------------------------------------------------------- # WARNING: The use of this file is governed by the terms of the license agreement. # # This file was generated by AppWizard. # # To create a new project, use the AppWizard and select the appropriate # project type. Then open this file and modify its contents to meet your needs. # # This file is the main project file for the Server DLL. # #----------------------------------------------------------------------------- # Project specific settings #----------------------------------------------------------------------------- # Project Name: Server # Project Type: Dynamic-Link Library (DLL) # Platform: Win32 #----------------------------------------------------------------------------- # Source Files #----------------------------------------------------------------------------- # Server.cpp # Source files for the main DLL implementation. # Server.def # Module definition file for the DLL. # StdAfx.cpp # Source file for precompiled header. #----------------------------------------------------------------------------- # Resource Files #----------------------------------------------------------------------------- # Server.rc # Resource script for the DLL. #----------------------------------------------------------------------------- # Precompiled Header Files #----------------------------------------------------------------------------- # StdAfx.h # Header file for precompiled header. #----------------------------------------------------------------------------- # Other Files #----------------------------------------------------------------------------- # ReadMe.txt # General information about the project. #----------------------------------------------------------------------------- # Build Options #----------------------------------------------------------------------------- # Debug Configuration: # Compiler: /nologo /MDd /W3 /Gm /Zi /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /D "_WINDLL" /D "_AFXDLL" # Linker: /nologo /subsystem:windows /dll /debug /machine:I386 # Release Configuration: # Compiler: /nologo /MD /W3 /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_WINDLL" /D "_AFXDLL" # Linker: /nologo /subsystem:windows /dll /machine:I386 #----------------------------------------------------------------------------- ``` -------------------------------- ### PluginVideo DLL Structure and Notes Source: https://github.com/doge-1satellite/ttt2/blob/main/PluginVideo/ReadMe.txt Provides an overview of the PluginVideo DLL project, including its main components and build considerations. It highlights the project file, the primary source file, and precompiled header files. It also mentions the default behavior of not exporting symbols and how to modify this. ```cpp // PluginVideo.cpp: Main DLL source file // // When created, this DLL does not export any symbols. As a result, it // will not produce a .lib file when it is built. If you wish this project // to be a project dependency of some other project, you will either need to // add code to export some symbols from the DLL so that an export library // will be produced, or you can check the "doesn't produce lib" checkbox in // the Linker settings page for this project. // StdAfx.h, StdAfx.cpp: Used to build a precompiled header (PCH) file // named PluginVideo.pch and a precompiled types file named StdAfx.obj. // AppWizard uses "TODO:" to indicate parts of the source code you // should add to or customize. ``` -------------------------------- ### Client RAT Features Overview Source: https://github.com/doge-1satellite/ttt2/blob/main/Client/ReadMe.txt This section outlines the core functionalities of the Client RAT, detailing its capabilities in file management, screen monitoring, keylogging, remote terminal access, system management, video surveillance, session management, and other miscellaneous features. It also mentions the integration of IP geolocation. ```APIDOC Client RAT Features: File Management: - Mimics Radmin functionality. - Supports batch upload, delete, download, creation, and renaming of files and folders. Screen Monitoring: - Implemented entirely in assembly for high-speed data transfer. - Allows remote screen control, sending Ctrl+Alt+Del, and offers 7 color display modes. Keylogging: - Capable of recording both English and Chinese characters. - Supports offline recording with a limit of 50MB. Remote Terminal: - Provides a simple shell interface for command execution. System Management: - Includes process management, window management, and retrieval of dial-up connection passwords. Video Surveillance: - Enables monitoring of remote cameras. Session Management: - Functions include logoff, reboot, shutdown, and uninstallation of the server component. Other Functions: - Download and execute programs from specified URLs. - Hide or display access to specified websites. - Clear system logs. IP Geolocation: - Displays geographical location by placing the QQWry.Dat file in the program directory. Cluster Control: - Allows simultaneous control of multiple hosts. - Supports concurrent execution of video monitoring and other management functions. ``` -------------------------------- ### Client RAT Technical Architecture Source: https://github.com/doge-1satellite/ttt2/blob/main/Client/ReadMe.txt This section details the technical underpinnings of Client RAT, including its communication model, data transfer methods, and operational characteristics. It highlights the use of IOCP, zlib compression, and system service integration for stealth and efficiency. ```APIDOC Client RAT Technical Architecture: Communication Model: - Both control and server components utilize the IOCP (I/O Completion Port) model. Data Transfer: - Data transmission is performed using zlib compression. Performance: - Stable and fast operation. - No upper limit on the number of online hosts. - Capable of controlling tens of thousands of hosts simultaneously. Resource Management: - The control component automatically adjusts its working threads based on CPU usage for stable and efficient performance. Deployment: - The host process runs as a system service under svchost. - Hosts connect at two-minute intervals. Connectivity: - Features a heartbeat mechanism to prevent accidental disconnections. - Supports both HTTP and DNS for establishing connections. Stealth Features: - Automatically restores SSDT (functionality commonly used for anti-detection, user discretion advised for implementation). Component Size: - Control component: 224KB. - Generated server component: 156KB, uncompressed. - Allows for repeated installations; a 2-second delay is required between installations, and the guardian thread must be exited first. User Interface: - The control component features a minimalist interface. ``` -------------------------------- ### Server.cpp - Main DLL Source File Source: https://github.com/doge-1satellite/ttt2/blob/main/Server/ReadMe.txt This is the primary source file for the Server DLL. By default, it does not export any symbols, meaning it won't produce an export library (.lib file) when built. To enable symbol export, you need to add code to export symbols or adjust the Linker settings in the project configuration. ```cpp // Server.cpp : Defines the initialization routines for the DLL. // #include "pch.h" #include "framework.h" #include "Server.h" #ifdef _DEBUG #define new DEBUG_MAP #endif // CServerApp BEGIN_MESSAGE_MAP(CServerApp, CWinApp) END_MESSAGE_MAP() // CServerApp construction CServerApp::CServerApp() { // TODO: add construction code here, // Place all the common initialization code here } // The one and only CServerApp object CServerApp theApp; // CServerApp initialization BOOL CServerApp::InitInstance() { CWinApp::InitInstance(); // TODO: Add your own initialization code here return TRUE; } ``` -------------------------------- ### ShellCode.dsp - Project File Source: https://github.com/doge-1satellite/ttt2/blob/main/ShellCode/ReadMe.txt The ShellCode.dsp file is the project file used by AppWizard to manage the build process of the ShellCode application. It contains project-level information and is essential for compiling and linking the application. ```cpp // This file (the project file) contains information at the project level and is used to build a single project or subproject. // Other users can share the project (.dsp) file, but they should export the makefiles locally. ``` -------------------------------- ### libcef.dsp - Project File Source: https://github.com/doge-1satellite/ttt2/blob/main/libcef/ReadMe.txt The libcef.dsp file serves as the project file for the libcef DLL. It contains project-level information and is used for building the project or subprojects. This file can be shared among users, but they should export makefiles locally. ```dsp // libcef.dsp // Project file for the libcef DLL. // Contains information at the project level and is used to build a single project or subproject. // Other users can share the project (.dsp) file, but they should export the makefiles locally. ``` -------------------------------- ### Shell Project File Source: https://github.com/doge-1satellite/ttt2/blob/main/shell/ReadMe.txt The shell.dsp file is the project file for the shell DLL. It contains project-level information and is used to build the project or subprojects. This file can be shared among users, but they should export makefiles locally. ```dsp // shell.dsp // This file (the project file) contains information at the project level and // is used to build a single project or subproject. Other users can share the // project (.dsp) file, but they should export the makefiles locally. ``` -------------------------------- ### Baidu Map Initialization and Controls (JavaScript) Source: https://github.com/doge-1satellite/ttt2/blob/main/Client/res/Html/Baidu.html This snippet initializes a Baidu Map instance, sets its center based on URL parameters (longitude and latitude), adds a marker, and enables various interactive features and controls for an enhanced user experience. ```javascript function getParam(paramName) { paramValue = "", isFound = !1; if (this.location.search.indexOf("?") == 0 && this.location.search.indexOf("=") > 1) { arrSource = unescape(this.location.search).substring(1, this.location.search.length).split("&"), i = 0; while (i < arrSource.length && !isFound) arrSource[i].indexOf("=") > 0 && arrSource[i].split("=")[0].toLowerCase() == paramName.toLowerCase() && (paramValue = arrSource[i].split("=")[1], isFound = !0), i++ } return paramValue == "" && (paramValue = null), paramValue } var map = new BMap.Map("container"); var point = new BMap.Point(getParam("lng"), getParam("lat")); map.centerAndZoom(point, 14); var mark = new BMap.Marker(point); map.addOverlay(mark); map.enableInertialDragging(); map.enableContinuousZoom(); map.enableScrollWheelZoom(); map.enableKeyboard(); map.addControl(new BMap.NavigationControl({enableGeolocation:true})); map.addControl(new BMap.MapTypeControl()); map.addControl(new BMap.PanoramaControl({offset:new BMap.Size(20, 40)})); map.addControl(new BMap.ScaleControl({offset:new BMap.Size(0, 40)})); map.addControl(new BMap.OverviewMapControl()); ``` -------------------------------- ### ShellCode.cpp - Main Application Source File Source: https://github.com/doge-1satellite/ttt2/blob/main/ShellCode/ReadMe.txt This C++ file serves as the primary source code for the ShellCode application. It contains the main entry point and core logic of the console application. ```cpp // This is the main application source file. // AppWizard uses "TODO:" to indicate parts of the source code you should add to or customize. ``` -------------------------------- ### Baidu Map Initialization and Controls (JavaScript) Source: https://github.com/doge-1satellite/ttt2/blob/main/Bin/Plugins/Baidu.html This snippet initializes a Baidu Map instance, sets its center based on URL parameters (longitude and latitude), adds a marker, and enables various interactive features and controls for an enhanced user experience. ```javascript function getParam(paramName) { paramValue = "", isFound = !1; if (this.location.search.indexOf("?") == 0 && this.location.search.indexOf("=") > 1) { arrSource = unescape(this.location.search).substring(1, this.location.search.length).split("&"), i = 0; while (i < arrSource.length && !isFound) arrSource[i].indexOf("=") > 0 && arrSource[i].split("=")[0].toLowerCase() == paramName.toLowerCase() && (paramValue = arrSource[i].split("=")[1], isFound = !0), i++ } return paramValue == "" && (paramValue = null), paramValue } var map = new BMap.Map("container"); var point = new BMap.Point(getParam("lng"), getParam("lat")); map.centerAndZoom(point, 14); var mark = new BMap.Marker(point); map.addOverlay(mark); map.enableInertialDragging(); map.enableContinuousZoom(); map.enableScrollWheelZoom(); map.enableKeyboard(); map.addControl(new BMap.NavigationControl({enableGeolocation:true})); map.addControl(new BMap.MapTypeControl()); map.addControl(new BMap.PanoramaControl({offset:new BMap.Size(20, 40)})); map.addControl(new BMap.ScaleControl({offset:new BMap.Size(0, 40)})); map.addControl(new BMap.OverviewMapControl()); ``` -------------------------------- ### Standard Precompiled Header Files Source: https://github.com/doge-1satellite/ttt2/blob/main/shell/ReadMe.txt StdAfx.h and StdAfx.cpp are standard files used to build a precompiled header (PCH) file named shell.pch and a precompiled types file named StdAfx.obj. ```cpp // StdAfx.h, StdAfx.cpp // These files are used to build a precompiled header (PCH) file // named shell.pch and a precompiled types file named StdAfx.obj. ``` -------------------------------- ### StdAfx.h and StdAfx.cpp - Precompiled Header Source: https://github.com/doge-1satellite/ttt2/blob/main/Server/ReadMe.txt These files, StdAfx.h and StdAfx.cpp, are used to create a precompiled header (PCH) file named Server.pch and a precompiled types file named StdAfx.obj. Precompiled headers can significantly speed up compilation times by pre-compiling frequently used header files. ```cpp // StdAfx.h : include file for standard system include files, // or project specific include files that are used frequently, // but are changed infrequently #if !defined(AFX_STDAFX_H__XXXXXXXX_XXXX_XXXX_XXXX_XXXXXXXXXXXX__INCLUDED_) #define AFX_STDAFX_H__XXXXXXXX_XXXX_XXXX_XXXX_XXXXXXXXXXXX__INCLUDED_ #if _MSC_VER > 1000 #pragma once #endif #define VC_EXTRALEAN #include #include #ifndef _AFXDLL #error include "pch.h" instead of this file for PCH #endif // Other common includes // TODO: Add your specific includes here //{{AFX_INSERT_LOCATION}} // Microsoft Visual C++ will insert additional declarations immediately before the previous line. #endif // !defined(AFX_STDAFX_H__XXXXXXXX_XXXX_XXXX_XXXX_XXXXXXXXXXXX__INCLUDED_) // StdAfx.cpp : source file that includes just the standard includes // Server.pch will be the pre-compiled header and StdAfx.obj will be the pre-compiled type #include "pch.h" // When you are using precompiled headers, this source file is necessary for compilation to succeed ``` -------------------------------- ### StdAfx.h and StdAfx.cpp - Precompiled Header Files Source: https://github.com/doge-1satellite/ttt2/blob/main/ShellCode/ReadMe.txt These C++ files, StdAfx.h and StdAfx.cpp, are used to generate precompiled header (PCH) files, specifically 'ShellCode.pch' and 'StdAfx.obj'. This process helps to speed up compilation times. ```cpp // These files are used to build a precompiled header (PCH) file named ShellCode.pch and a precompiled types file named StdAfx.obj. ``` -------------------------------- ### StdAfx.h and StdAfx.cpp - Precompiled Headers Source: https://github.com/doge-1satellite/ttt2/blob/main/libcef/ReadMe.txt These files, StdAfx.h and StdAfx.cpp, are utilized for building a precompiled header (PCH) file named libcef.pch and a precompiled types file named StdAfx.obj. Precompiled headers help speed up the compilation process. ```cpp // StdAfx.h, StdAfx.cpp // Used to build a precompiled header (PCH) file named libcef.pch and a precompiled types file named StdAfx.obj. ``` -------------------------------- ### Shell DLL Main Source File Source: https://github.com/doge-1satellite/ttt2/blob/main/shell/ReadMe.txt This C++ file is the main source file for the shell DLL. It currently does not export any symbols, meaning it won't produce a .lib file when built. To make it a project dependency, symbols need to be exported, or the 'doesn't produce lib' linker setting should be enabled. ```cpp // shell.cpp // This is the main DLL source file. // When created, this DLL does not export any symbols. As a result, it // will not produce a .lib file when it is built. If you wish this project // to be a project dependency of some other project, you will either need to // add code to export some symbols from the DLL so that an export library // will be produced, or you can check the "doesn't produce lib" checkbox in // the Linker settings page for this project. ``` -------------------------------- ### libcef.cpp - Main DLL Source File Source: https://github.com/doge-1satellite/ttt2/blob/main/libcef/ReadMe.txt This is the primary source file for the libcef DLL. It initially does not export any symbols, meaning it won't produce an export library (.lib file) upon building. To make it a project dependency, symbols need to be exported, or the 'doesn't produce lib' linker option should be enabled. ```cpp // libcef.cpp // Main DLL source file. // When created, this DLL does not export any symbols. As a result, it // will not produce a .lib file when it is built. If you wish this project // to be a project dependency of some other project, you will either need to // add code to export some symbols from the DLL so that an export library // will be produced, or you can check the "doesn't produce lib" checkbox in // the Linker settings page for this project. ``` -------------------------------- ### Baidu Map CSS Styling Source: https://github.com/doge-1satellite/ttt2/blob/main/Client/res/Html/Baidu.html This CSS defines the basic styling for the Baidu Map container, ensuring it occupies the full width and height of its parent element and sets the default font size. ```html html, body, #container {width:100%;height:100%;overflow:hidden;margin:0;font-size:13px;} ``` -------------------------------- ### Gaode Map CSS Styling Source: https://github.com/doge-1satellite/ttt2/blob/main/Client/res/Html/Gaode.html Basic CSS rules to ensure the Gaode Map container occupies the full width and height of its parent element, with no overflow and default font styling. ```css html, body, #container {width:100%;height:100%;overflow:hidden;margin:0;font-size:13px;} ``` -------------------------------- ### Baidu Map CSS Styling Source: https://github.com/doge-1satellite/ttt2/blob/main/Bin/Plugins/Baidu.html This CSS defines the basic styling for the Baidu Map container, ensuring it occupies the full width and height of its parent element and sets the default font size. ```html html, body, #container {width:100%;height:100%;overflow:hidden;margin:0;font-size:13px;} ``` -------------------------------- ### Gaode Map CSS Styling Source: https://github.com/doge-1satellite/ttt2/blob/main/Bin/Plugins/Gaode.html Basic CSS rules to ensure the Gaode Map container occupies the full width and height of its parent element, with no overflow and default font styling. ```css html, body, #container {width:100%;height:100%;overflow:hidden;margin:0;font-size:13px;} ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.