CraxsRat Source Code

This repository contains the leaked source code of CraxsRat, a sophisticated Android remote access trojan (RAT) developed by "EVLF DEV". CraxsRat has been used in various cyber-attacks to grant cybercriminals extensive control over infected devices.

Disclaimer

Warning: Im not the code writer ,the source code got leaked by another person on telegram, This repository contains malicious code and is intended for cybersecurity research and educational purposes only. The use of this code for any unauthorized or illegal activities is strictly prohibited and punishable by law. By using this code, you agree to use it responsibly and comply with all applicable laws and regulations.

Features

• Device Location Retrieval: Obtain the precise location of the infected device.
• Contact Exfiltration: Extract contacts from the device.
• Storage Access: Access and manipulate files stored on the device.
• Message and Call Log Compromise: Access and manipulate SMS messages and call logs.
• Obfuscation and Anti-Removal: Generate highly obfuscated packages to evade detection and prevent removal.
• Accessibility Exploitation: Modify the accessibility settings page to maintain persistence.
• Google Play Protect Bypass: The latest version, v7.4, can bypass Google’s built-in antivirus system, Google Play Protect.

Installation

Directory Descriptions

Directories

1. .vs

   • Visual Studio project settings and configuration files.

2. bin

   • Directory containing compiled binaries and executable files for the project.

3. My

   • Possibly a user-defined directory for additional resources or files.

4. obj

   • Intermediate files and object files generated during the build process.

5. Properties

   • Directory containing project properties and settings, typically includes AssemblyInfo.cs.

Files

1. -Module-.cs

   • Placeholder or template module file.

2. -Module-{14C782A-EBF2-4C59-8120-8B1FAF654264}.cs

   • Module file with a unique identifier in its name.

3. -ProjectType-.cs

   • Placeholder or template project type file.

4. 1.cs

   • Source code file, likely one of the early files in the project.

5. 1~1.cs

   • Backup or temporary file for 1.cs.

6. 2.cs

   • Another source code file, possibly a continuation or related to 1.cs.

7. 2~1.cs

   • Backup or temporary file for 2.cs.

8. 3.cs

   • Another source code file, following 2.cs.

9. 3~1.cs

   • Backup or temporary file for 3.cs.

10. 4.cs

    • Another source code file, following 3.cs.

11. 4~1.cs

    • Backup or temporary file for 4.cs.

12. 5.cs

    • Another source code file, following 4.cs.

13. 5~1.cs

    • Backup or temporary file for 5.cs.

14. 6.cs

    • Another source code file, following 5.cs.

15. 6~1.cs

    • Backup or temporary file for 6.cs.

16. AssemblyInfo.cs

    • Contains metadata about the assembly, such as version information and attributes.

17. App.xaml

    • Defines the application-level properties, resources, and event handlers.

18. App.xaml.cs

    • Code-behind file for App.xaml, containing application logic.

19. MainWindow.xaml

    • Defines the user interface for the main window of the application.

20. MainWindow.xaml.cs

    • Code-behind file for MainWindow.xaml, containing the logic for the main window.

21. PrismModuleA.csproj

    • Project file for the PrismModuleA project, containing build configurations and project settings.

22. PrismModuleA.csproj.user

    • User-specific project settings, such as user preferences and settings.

23. Sample.xlam

    • Excel Add-In file, likely a sample or template for Excel extensions.

24. sample1.csv

    • Sample CSV file, possibly containing data for testing or demonstration.

25. Template.xaml

    • Defines a XAML template, potentially for UI components or styles.

Requirements

• Android device (target)
• Builder application to create the RAT payload

Setup

1. Clone the Repository:

   git clone https://github.com/maxamin/CraxsRat-v6.7-Source-Code.git
   cd craxsrat-source-code

2. Builder Configuration:

   • Follow the instructions in the builder directory to set up and configure the RAT payload.
   • Customize the payload to suit your specific requirements.

3. Payload Deployment:

   • Distribute the RAT payload through social engineering, malvertising, or other methods.
   • Ensure the payload is installed on the target device.

Usage

1. Control the Infected Device:

   • Use the command and control (C2) server to send commands to the infected device.
   • Retrieve location, contacts, messages, call logs, and access stored files.

2. Maintain Persistence:

   • Utilize the obfuscation features to keep the RAT hidden from the user and security software.
   • Ensure the RAT's accessibility settings are enabled to maintain control over the device.