Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyΒ© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
BL00DYM4RY β€” Educational trojan simulator for cybersecurity training, simulating phishing attacks with social engineering, system reconnaissance, anti-sandbox evasion, and data exfiltration to raise awareness. | Kitploit
Tools/GitLabGitLab/toxy4ny/bl00dym4ry
Data ExfiltrationInformation GatheringPhishingSocial EngineeringLearning & EducationRed TeamingPayload Development
GitLabtoxy4ny/bl00dym4ry

BL00DYM4RY

Educational trojan simulator for cybersecurity training, simulating phishing attacks with social engineering, system reconnaissance, anti-sandbox evasion, and data exfiltration to raise awareness.

View Repository
862 months agoNot yet reviewed

Most Popular

View all β†’

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools β†’
Share
Website

🎭 BloodyMary Trojan Phishing Simulator

πŸ“‹ Description

BloodyMary is an educational tool (trojan-virus or Ransomware) for training cybersecurity specialists, simulating realistic phishing attacks with social engineering elements. This project was created to raise awareness about cyber threats and demonstrate the consequences of running suspicious files.

⚠️ WARNING: This tool is intended EXCLUSIVELY for educational purposes and authorized testing in controlled environments.


🎯 Project Goals

  • Training personnel in cybersecurity fundamentals
  • Demonstrating realistic phishing techniques
  • Raising awareness about social engineering
  • Testing readiness for cyber threats

πŸ”§ Technical Capabilities

πŸ•΅οΈ Reconnaissance Techniques

  • βœ… System information gathering (OS, processor, RAM)
  • βœ… Network configuration analysis (IP, MAC, adapters)
  • βœ… Active process enumeration
  • βœ… Username and computer name identification

πŸ›‘οΈ Anti-Sandbox

  • βœ… Execution time verification (bypass time acceleration)
  • βœ… Process count analysis (sandbox detection)
  • βœ… RAM volume checking (VM detection)
  • βœ… Activation delay (behavioral analysis evasion)

πŸ“‘ Data Exfiltration

  • βœ… TCP transmission (SSH imitation)
  • βœ… HTTP fallback for reliability
  • βœ… Network settings obfuscation
  • βœ… Unique filename generation

🎭 Social Engineering

  • βœ… Realistic visual effects
  • βœ… Psychological impact
  • βœ… Ransomware behavior imitation
  • βœ… Educational messages

🎬 Gaming Elements

🩸 Visual Effects

  • Realistic Blood: Physical simulation of drops with gravity
  • Ghostly Messages: Flickering text with glow effect
  • Fullscreen Animation: Optimized for Full HD (1920x1080)
  • Double Buffering: Smooth animation without flickering

🎨 Effect Technical Details

// Blood drop physics
drops[i].velocityY += drops[i].acceleration;
drops[i].x += drops[i].velocityX;
drops[i].y += drops[i].velocityY;

// Color gradient creation
COLORREF CreateBloodGradient(int baseRed, int variation, int alpha)

πŸŽͺ Impact Scenario

  1. Stealth Launch - No visible signs
  2. Data Collection - Silent system analysis
  3. Anti-Sandbox - Virtual environment check
  4. Exfiltration - Data transmission to "C&C server"
  5. Psychological Effect - Dramatic visualization
  6. Educational Finale - Explanation of what happened

πŸ› οΈ Build and Installation

Requirements

  • Arch Linux (or any Linux with MinGW-w64)
  • MinGW-w64 cross-compiler
  • UPX for compression (optional)
  • Wine for testing (optional)

Quick Installation

# Install dependencies
sudo pacman -S mingw-w64-gcc mingw-w64-binutils mingw-w64-headers mingw-w64-crt upx wine

# Clone repository
git clone https://github.com/toxy4ny/bl00dym4ry.git
cd bl00dym4ry

# Build
make
# or
./build.sh

# Build both versions (32-bit and 64-bit)
make all
# or
./build.sh all

Manual Build

# 64-bit version
x86_64-w64-mingw32-gcc -Os -s -static -DWIN32_LEAN_AND_MEAN \
    -ffunction-sections -fdata-sections -fno-ident -fomit-frame-pointer \
    -o bl00dym3ry.exe main.c \
    -Wl,--gc-sections -Wl,--strip-all -Wl,--build-id=none \
    -static-libgcc -static-libstdc++ \
    -lwininet -lws2_32 -liphlpapi -luser32 -lkernel32 -lgdi32 \
    -lshell32 -ladvapi32 -lole32 -loleaut32 -luuid -lmsimg32

# Size optimization
x86_64-w64-mingw32-strip --strip-all bl00dym3ry.exe
upx --best --lzma bl00dym3ry.exe

πŸŽ“ Educational Scenarios

πŸ“§ Phishing Campaigns

  1. Email Attachment: Disguised as document or image
  2. USB Drop: Placed on USB drive with attractive name
  3. Social Media: Distributed as "interesting file"
  4. Corporate Network: Test employee awareness

🎯 Target Groups

  • IT Specialists - Technical threat understanding
  • Managers - Business risk comprehension
  • Regular Users - Cybersecurity hygiene basics
  • Students - Practical learning

πŸ“Š Reporting

Automatic Reports

  • Desktop Report: SECURITY_TRAINING_REPORT.txt on desktop
  • Remote Logging: Server transmission for analysis
  • Timestamp: Precise execution time
  • System Fingerprint: Unique system identification

Report Structure

===============================================================
                    CYBERSECURITY TRAINING REPORT
===============================================================

WARNING: This is the result of a phishing training test

YOU SUCCESSFULLY LAUNCHED A SUSPICIOUS FILE!

What happened:
+ System information was collected
+ Data was sent to external server
+ Visual effects were demonstrated
+ Malicious activity was simulated

RECOMMENDATIONS:
1. Don't open suspicious attachments
2. Verify email senders
3. Use antivirus software
4. Regularly update software
5. Be careful with links

πŸ”’ Security and Ethics

βœ… Legal Usage

  • Authorized testing in own infrastructure
  • Educational programs with participant consent
  • Threat demonstration in controlled environment
  • Corporate cybersecurity training

❌ Prohibited Usage

  • Attacks on foreign systems without permission
  • Causing real harm or damage
  • Violating computer crime legislation
  • Commercial use without license

πŸ›‘οΈ Safety Measures

// File does NOT cause real harm:
// - Does not encrypt files
// - Does not install backdoors
// - Does not modify system settings
// - Creates only educational report

πŸŽ₯ Operation Demonstration

Phase 1: Stealth Launch

[βœ“] Anti-sandbox checks passed
[βœ“] Console window hidden
[βœ“] Process started successfully

Phase 2: Reconnaissance

[βœ“] System information collected
[βœ“] Network configuration analyzed  
[βœ“] Process enumeration completed
[βœ“] User credentials identified

Phase 3: Exfiltration

[βœ“] Data packaged for transmission
[βœ“] TCP connection established
[βœ“] Information sent to C&C server
[βœ“] Connection terminated

Phase 4: Psychological Impact

[βœ“] Screen effects activated
[βœ“] Horror elements displayed
[βœ“] Victim awareness achieved
[βœ“] Educational message delivered

πŸ”§ Configuration and Customization

Network Settings

// Change obfuscated SSH settings
static char ssh_host[] = {0x73, 0x7f, 0x7f, 0x3a, 0x66, 0x6d, 0x63, 0x3a, 0x66, 0x3a, 0x66, 0x72, 0x72, 0x00};
static char ssh_user[] = {0x05, 0x16, 0x17, 0x03, 0x16, 0x02, 0x03, 0x00};
static char ssh_pass[] = {0x08, 0x34, 0x09, 0x16, 0x01, 0x02, 0x16, 0x08, 0x67, 0x65, 0x67, 0x69, 0x00};

Visual Effects

// Blood intensity configuration
#define BLOOD_DROPS_COUNT 80
#define BLOOD_SPLATTERS_COUNT 150
#define BLOOD_TRAILS_COUNT 300
#define ANIMATION_FRAMES 500

Anti-Sandbox

// Check configuration
#define MIN_SLEEP_TIME 2800
#define MIN_PROCESS_COUNT 25
#define MIN_RAM_SIZE (1024 * 1024 * 1024)

πŸ“š Educational Materials

πŸŽ“ For Instructors

  • Use as practical assignment
  • Explain each technique after demonstration
  • Discuss protection methods
  • Conduct debriefing with participants

πŸ”¬ For Researchers

  • Analyze evasion techniques
  • Study obfuscation methods
  • Develop countermeasures
  • Improve detection systems

πŸ‘₯ For HR and Management

  • Demonstrate real risks
  • Justify security investments
  • Raise personnel awareness
  • Create security culture

🀝 Project Participation

πŸ› Bug Reports

If you found a bug or issue:

  1. Check existing issues
  2. Create new issue with detailed description
  3. Attach system information
  4. Specify reproduction steps

πŸ’‘ Improvement Suggestions

  • New evasion techniques
  • Additional visual effects
  • Information gathering improvements
  • Performance optimization

πŸ› οΈ Pull Requests

  1. Fork repository
  2. Create feature branch
  3. Make changes
  4. Write tests
  5. Create pull request

πŸ“„ License

Download Tool