GitPedia

Fortnite external

Fairly advanced Fortnite external framework built around a custom kernel driver and stealth-oriented memory access architecture.

From d0do47·Updated June 15, 2026·View on GitHub·

originally named hypervisor.solutions (hv.sol), was leaked off my drive and was made open-source. The project is written primarily in C++, first published in 2023. Key topics include: battleye-bypass, eac-bypass, fortnite, fortnite-aimbot, fortnite-cheat.

fortnite-external

originally named hypervisor.solutions (hv.sol), was leaked off my drive and was made open-source.

Overview

Fairly advanced Fortnite external framework built around a custom kernel driver and stealth-oriented memory access architecture.

The project is not just an ESP/aimbot source — it’s structured more like a reusable reversing base containing:

  • kernel memory primitives
  • anti-detection concepts
  • import obfuscation
  • Unreal Engine object parsing
  • rendering/aim systems
  • syscall & driver communication layers
  • dynamic API resolution

The codebase resembles modern private cheat architecture more than older pasted externals.


Architecture

Usermode Client

Custom Communication Layer

Kernel Driver

Physical / Virtual Memory Access

Fortnite Process Interaction


Driver Project

Kernel-Mode Driver

The driver is the most important part of the repo.

Core responsibilities:

  • privileged memory R/W
  • page table translation
  • protected memory access
  • bypassing usermode handle restrictions
  • exposing IOCTL interface to usermode

The driver appears designed specifically for anti-cheat resistance.


Physical Memory Access

The driver likely uses:

  • CR3 swapping / DTB retrieval
  • MmCopyMemory
  • physical address translation
  • manual page walking
  • virtual → physical mapping

Instead of relying purely on:

cpp
MmCopyVirtualMemory

This is a major difference between beginner projects and more serious frameworks.


Dynamic Imports

The repo appears to avoid static imports in multiple places.

Typical techniques used:

  • hashed API resolution
  • runtime export walking
  • manual GetProcAddress
  • PEB traversal
  • lazy imports
  • encrypted/import-hidden WinAPI calls

Purpose:

  • reduce static signatures
  • avoid import table detection
  • make reversing harder
  • lower heuristic detection risk

Instead of:

cpp
CreateFileA(...)

it resolves APIs dynamically at runtime.


Manual Mapping / Stealth Concepts

The project contains signs of stealth-focused loading concepts such as:

  • stripped imports
  • hidden driver communication
  • indirect syscalls
  • minimized WinAPI exposure
  • custom communication structures

Possibly includes:

  • PiDDBCache cleaning
  • MmUnloadedDrivers cleanup
  • trace reduction logic
  • driver hiding concepts

These are common in modern kernel cheat frameworks.


Usermode Layer

Driver Communication

The usermode client communicates with the driver using:

  • IOCTL requests
  • shared structures
  • custom packets
  • read/write dispatch routines

This acts as the bridge between Fortnite and the kernel backend.


Unreal Engine SDK Layer

Contains Fortnite SDK structures for:

  • UWorld
  • APlayerController
  • AActor
  • USkeletalMeshComponent
  • FTransform
  • CameraCache
  • weapon/projectile data

Used to traverse live game memory.


Actor & Entity System

The project maintains entity caching systems for:

  • players
  • bots
  • loot
  • vehicles
  • weakspots
  • projectiles

Likely optimized to avoid excessive memory reads.


Rendering System

ESP / Overlay

Includes rendering code for:

  • corner boxes
  • skeleton ESP
  • snaplines
  • radar
  • distance text
  • platform labels
  • weapon names

Usually implemented through:

  • DirectX overlays
  • transparent layered windows
  • external rendering contexts

World-to-Screen Math

Includes:

  • camera extraction
  • projection matrices
  • bone transforms
  • visibility math
  • vector calculations

Core Unreal Engine rendering math.


Aim System

Contains logic for:

  • target selection
  • closest bone targeting
  • FOV restriction
  • smoothing
  • prediction
  • visibility checks
  • recoil/spread handling

Likely supports configurable hitboxes:

  • head
  • neck
  • chest

Updating

The repo appears setup in a modular sense for quick game patch updates.

Contains:

  • centralized offsets
  • SDK dumps
  • pattern scanning/signatures
  • offset abstraction

Do not attempt to update or rework this project again. Most modern copies of this repo are heavily pasted, poorly maintained, and not worth salvaging.

Save yourself the time and build from a cleaner base instead of trying to repair layered spaghetti code.


Reverse Engineering Features

The codebase heavily uses RE-oriented concepts:

  • signature scanning
  • pointer chain traversal
  • guarded region handling
  • encrypted pointer handling
  • Unreal object traversal
  • engine-specific structures

Overall Assessment

This is significantly more advanced than a pasted “public cheat source.”

The important parts are:

  • the kernel driver architecture
  • stealth-oriented import resolution
  • memory translation logic
  • modular Unreal Engine parsing

The repo is essentially:

  • a Fortnite reversing framework
  • a kernel memory toolkit
  • an external rendering/aim platform
  • an anti-detection research project

all combined into one codebase.

Contributors

Showing top 1 contributor by commit count.

View all contributors on GitHub →

This article is auto-generated from d0do47/fortnite-external via the GitHub API.Last fetched: 6/28/2026