Hardware identifier management tool for Windows 10 / 11 (x64)

HWID Spoofer is an open-source Windows utility for reading, backing up, and temporarily modifying hardware identifiers used by software and games for device fingerprinting. Built for researchers, developers, and power users who need to test fingerprinting logic on their own machines.

• Read current disk serial, SMBIOS UUID, MAC address, and volume IDs
• One-click backup of original identifiers before any change
• Restore original values on reboot or via manual restore
• Clean CLI and optional GUI — no bundled third-party tools
• Fully auditable C++ source — build it yourself

Disclaimer: Use only on systems you own. You are responsible for compliance with applicable laws and software terms of service.

Linux and macOS are not supported. This project targets the Windows hardware stack only.

1. Go to Releases
2. Download HWIDSpoofer-x64.zip
3. Extract and run .exe as Administrator
4. Use backup before any spoof operation

git clone https://github.com/your-username/hwid-spoofer.git
cd hwid-spoofer
cmake -B build -G "Visual Studio 17 2022" -A x64
cmake --build build --config Release

Output: build/Release/HWIDSpoofer.exe

HWIDSpoofer.exe [command] [options]

Commands:
  status          Show current hardware identifiers
  backup          Save snapshot to backup/hwid_backup.json
  restore         Restore from last backup
  spoof --all     Apply all enabled spoof modules
  spoof --disk    Disk serial only
  spoof --mac     Network MAC only
  spoof --smbios  SMBIOS fields only
  clean           Remove common fingerprint registry keys

Options:
  --seed <hex>    Deterministic random seed for serial generation
  --adapter <n>   Network adapter index (default: 0)
  --help          Show help

# 1. Check current IDs
.\HWIDSpoofer.exe status

# 2. Backup originals
.\HWIDSpoofer.exe backup

# 3. Spoof everything
.\HWIDSpoofer.exe spoof --all

# 4. Reboot, then restore when done testing
.\HWIDSpoofer.exe restore

HWIDSpoofer.exe
       │
       ├─ 1. Enumerate hardware (WMI + SetupAPI + registry)
       ├─ 2. Backup → backup/hwid_backup.json
       ├─ 3. Spoof modules (user-mode + optional kernel driver)
       │      ├─ DiskSerialSpoofer
       │      ├─ SmbiosSpoofer
       │      ├─ MacSpoofer
       │      └─ VolumeSerialSpoofer
       └─ 4. Restore on demand or after reboot (configurable)

See docs/architecture.md for module-level details.

hwid-spoofer/
├── .github/
│   ├── workflows/
│   │   └── auto-commit.yml      # Auto-update every 30 min
│   ├── ISSUE_TEMPLATE/
│   └── FUNDING.yml
├── assets/
│   ├── banner.svg               # README banner
│   └── logo.svg                 # Project logo
├── docs/
│   ├── architecture.md
│   ├── build.md
│   └── faq.md
├── src/
│   ├── core/                    # Backup, config, logging
│   ├── modules/                 # Spoof implementations
│   ├── cli/                     # Command-line interface
│   └── gui/                     # Optional Win32 GUI
├── driver/                      # Optional kernel driver (WDK)
├── backup/                      # Local backup storage (gitignored)
├── preview.png                  # GitHub social preview (1280×640)
├── preview.svg                  # Vector preview
├── button.svg                   # Download button for README
├── last-updated.txt             # Updated by CI
├── CMakeLists.txt
└── LICENSE

Q: Will this work after a game ban?
A: This tool modifies local identifiers for testing. Effectiveness depends on what the target software fingerprints. No guarantees — review docs/faq.md.

Q: Do I need the kernel driver?
A: User-mode covers MAC, registry, and volume serial. Disk/SMBIOS spoofing at the block level requires the optional driver/ module and test-signing or a proper code-signing certificate.

Q: Windows Defender flags the EXE — is it safe?
A: HWID tools often trigger heuristics. This repo is open source — audit the code and build locally. See docs/build.md.

Q: Are changes permanent?
A: No. Use restore or reboot (depending on module). Always run backup first.

Contributions welcome. For large changes, open an issue first.

1. Fork the repository
2. Create a branch: git checkout -b feature/my-module
3. Commit with clear messages
4. Open a Pull Request

See CONTRIBUTING.md for coding standards.

Found a vulnerability? Please read SECURITY.md — do not open public issues for security reports.

Distributed under the MIT License. See LICENSE for details.

_{Windows x64 · Open Source · For research on systems you own}