A Windows toolkit for inspecting, simulating, and managing system hardware identity values (Spoofer) for educational purposes ONLY.
- 75 π New Features
- Native C++ backend (
UmbrellaHelper.exe) β all hardware changes done in native Win32, not managed code - Style-preserving serial generation β spoofed values match the exact pattern of originals
- WMI repository cache writes β targets WMI backing storage so
Win32_*queries return spoofed values - Windows toast notifications for update availability
- Enhanced safety β no WMI reset, no ProductId changes, no network adapter toggling
- Hardware inventory view with live identifiers
- Style-preserving masked preview generation
- Temporary mode β reverts on reboot via RunOnce
- Permanent mode β persists until manual restore
- History and backup tracking with auto-backup
- System tray integration with balloon notifications
- Discord Rich Presence integration
- Configurable update checks via GitHub API
- Windows 10 or Windows 11
- .NET 8 Desktop Runtime or SDK
- Visual Studio 2022 C++ BuildTools (for compiling native helper)
- Administrator privileges
demo.mp4
git clone https://github.com/NikolisSecurity/UmbrellaSpoofer.git
cd UmbrellaSpoofer
start.batOr manually:
# Build native helper (requires MSVC)
call "C:\Program Files\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
NativeHelper\build.bat
# Build .NET projects
dotnet build
# Run
.\UmbrellaSpoofer\bin\Debug\net8.0-windows\UmbrellaSpoofer.exeC# (WPF UI) β UmbrellaSpoofer.exe β UI, preview generation, user input
C# (Core Library) β UmbrellaCore.dll β SpoofGenerator, proxy to native helper
C++ (Native Win32) β lib\UmbrellaHelper.exe β All registry writes, privilege escalation
| Component | Registry Path | Affects |
|---|---|---|
| MachineGuid | HKLM\SOFTWARE\Microsoft\Cryptography |
HWID binding |
| BIOS Serial | SystemInformation, Win32_BIOS |
System fingerprinting |
| BaseBoard Serial | SystemInformation, Win32_BaseBoard |
Motherboard ID |
| CPU Identifier | SystemInformation, WinSAT, Win32_Processor, Environment |
CPU fingerprinting |
| GPU Identifiers | Control\Class\{GPU}\* |
Graphics identity |
| MAC Address | Control\Class\{NET}\*\NetworkAddress |
Network identity |
| Volume Serials | EMDMgmt |
Volume tracking |
| TPM Identity | Control\Tpm, Services\TPM\WMI |
TPM metadata |
| SMBIOS Cache | Services\mssmbios\Data |
BIOS table cache |
| ACPI Strings | Control\ACPI\* |
ACPI table metadata |
| System Enclosure | SystemInformation |
Chassis/family info |
These cannot be spoofed from user mode:
- Actual disk serial (ATA IDENTIFY command)
- Actual RAM SPD serial (SMBus/IΒ²C)
- Actual CPUID instruction output
- Actual TPM endorsement key (hardware crypto)
- Actual monitor EDID (DDC/IΒ²C)
- Actual BIOS flash contents
The KernelDriver/ directory is reserved for future ring-0 development.
Configured via Settings tab or tray icon menu.
Checks https://api.github.com/repos/NikolisSecurity/UmbrellaSpoofer/releases/latest on startup. Shows tray notification + dialog when a new version is available. No auto-download.
- Does this bypass anti-cheat? No guarantees but it could work. Use responsibly and respect TOS.
- Will this harm my PC? All operations are safe informational registry writes. No services are stopped, no WMI is wiped, no network adapters are toggled, no license keys are modified.
- Do the changes persist after reboot? Yes. Registry writes are persistent. Use Temporary mode to auto-revert on next login.
- Why don't disk/RAM/EDID changes work? Those are read directly from hardware via ATA/SMBus/IΒ²C commands, not from registry. A kernel driver is required.
- Use this tool responsibly and at your own risk
- Modifying hardware identifiers may violate terms of service of some applications
- Some changes require administrator privileges
- This tool is for privacy and testing purposes only
- Run as administrator for all operations
- If native helper fails, ensure MSVC redistributables are installed
- If update checks fail, verify
updater.jsoncontains valid owner/repo - For serials not appearing to change, the target app may read directly from hardware (see "What Requires a Kernel Driver" above)
See LICENSE.
For issues or feature requests, please open an issue on the GitHub repository.