Easy Anti Tamper

Industrial-grade software protection for Windows

8 runtime shield guards, binary encryption, hardware-locked licensing, and a register-based VM. One SDK, zero kernel drivers.

Get Started → Download Demo
No kernel driver required Anti-cheat compatible ChaCha20 + BLAKE2b
cloud4.antitamper.co

Overview

Protection status across all your products

Products
0
Active Licenses
0
Total Keys
0
Activations 24h
0
Recent License KeysView all →
License keyProductStatusCreated
EAT-9F4A-7C21-B8E0Sentinel ProActive2h ago
EAT-3D72-1A55-C9F4VaultGuardActive5h ago
EAT-B610-44EF-0072Sentinel ProPending9h ago
EAT-7E88-92C0-3A1DCoreShieldActive1d ago

Products

3 products protected

Sentinel Pro
Anti-tamper + licensing + VM
5,142
active keys
VaultGuard
License vault + HWID binding
2,891
active keys
CoreShield
Full protection suite
1,171
active keys

License Keys

9,204 total keys across all products

All Keys+ Generate Keys
License keyProductStatusHWID
EAT-9F4A-7C21-B8E0Sentinel ProActivea7c2...9f1e
EAT-3D72-1A55-C9F4VaultGuardActiveb310...44ef
EAT-B610-44EF-0072Sentinel ProPending—
EAT-E4C0-88D1-6FA2CoreShieldRevokedc882...1d07
EAT-7E88-92C0-3A1DCoreShieldActivef91a...c3b8

Activity

Recent events across your products

activated EAT-9F4A-7C21 activated on Sentinel Pro 2m ago
created 10 new keys generated for VaultGuard 18m ago
tamper DebugGuard triggered on CoreShield — HWID c882...1d07 1h ago
revoked EAT-E4C0-88D1 revoked — license abuse 3h ago
heartbeat Health check OK — Sentinel Pro 218 active sessions 5h ago

Protection Suite

Defense in depth, by default

Eight coordinated shield guards plus binary encryption, a register-based VM, and hardware-locked licensing.

8 Runtime Shield Guards

DebugGuard, HookDetector, DumpGuard, InjectionGuard, MemoryGuard, ThreadGuard, TimingGuard, and ProcessGuard work in rotation to detect and respond to tampering in real time.

Binary Encryption

EAT.Publish strips your import table, encrypts code sections with ChaCha20, and scrubs all string literals. EAT.Runtime resolves everything at launch — nothing useful on disk.

Register-Based VM

Critical code paths run inside a register-based bytecode interpreter. No executable memory allocated — compatible with anti-cheat systems that block RWX pages.

Process Hardening

Injects OS-level mitigations at launch: DEP, ASLR, CFG, ACG, code signing restrictions, and DACL lockdown. Raises the floor for every exploit technique.

Hardware-Locked Licensing

BLAKE2b certificate chains bound to a weighted HWID fingerprint (CPU, GPU, TPM, motherboard). Encrypted vault with ChaCha20-Poly1305 — tolerates minor hardware changes.

Telemetry & Challenges

Heartbeat monitoring, tamper event reporting, and server-issued challenge/response verification. Know when someone is attacking your binary — in real time.

How It Works

Four steps from build to protected

01

Build your app

Compile normally with MSVC. Add EAT_INIT() and link the SDK — typically under 10 lines of code.

02

EAT.Publish processes

Post-build tool strips the import table, encrypts .sc code sections, scrubs string literals, and injects process mitigations.

03

Runtime resolves

EAT.Runtime decrypts sections, resolves imports, validates the license vault, and starts the 8 shield guards — all before your main() runs.

04

Cloud manages

Dashboard handles license keys, HWID bans, team members, telemetry, and Discord bot integration. Server challenges verify runtime integrity remotely.

Architecture

The protection pipeline

Three layers work together: a post-build tool transforms the binary, a runtime DLL protects it, and the cloud verifies it.

1

EAT.Publish

PE parser, IAT stripper, ChaCha20 section encryptor, string scrubber, mitigation injector. Lua script engine for custom protection profiles.

2

EAT.Runtime

In-process DLL. Decrypts code, resolves imports, validates vault, starts shield guards. TLS callback entry — runs before main.

3

EAT.Kernel32

Clean reimplementations of Windows APIs (bcrypt, etc.) to bypass hook-based interception. Runtime calls these instead of real system DLLs.

4

EAT Cloud

License key management, HWID banning, telemetry ingestion, challenge dispatch, crash reporting, and team/org management via REST API.

Pricing

Simple plans that scale with you

Monthly Yearly 2 months free
Free
Browse products and redeem licenses.
$0
  • Redeem & manage your licenses
  • Community access
Start Free
Seller
For solo developers shipping a few products.
$50/yr
  • Up to 3 products
  • 2 team members
  • License key generation
  • Analytics dashboard
  • Version management
Get Started
Most Popular
Pro
For studios that need the full platform.
$100/yr
  • Everything in Seller, plus
  • Up to 10 products
  • 5 team members
  • 1 GB file hosting
  • OAuth apps
  • Discord bot integration
  • HWID ban management
Get Started
Pro Plus
For teams at scale.
$200/yr
  • Everything in Pro, plus
  • 10 GB file hosting
  • Data export (GDPR)
Get Started
Enterprise
Unlimited everything, dedicated support.
Custom
  • Unlimited products & team
  • Unlimited storage
  • Priority support & SLA
  • Custom contracts
Contact Sales

All paid plans available monthly or yearly. Prices in USD.

Try It

Download our example application to see Easy Anti Tamper protection in action.

Download Demo

FAQ

Frequently asked questions

EAT targets Windows x64 applications built with MSVC. Integration is either static linking (compile with the SDK) or dynamic DLL loading at runtime. No kernel driver is required — everything runs in user mode.
EAT.Publish runs as a post-build step. It parses the PE, strips the import address table, encrypts marked code sections (.sc) with ChaCha20, and replaces all string literals with encrypted stubs. At runtime, EAT.Runtime decrypts sections in-place, resolves imports dynamically, and decrypts strings on demand. The binary on disk contains no readable code or strings.
Decryption and import resolution happen once at startup (typically under 50ms). Shield guards rotate across cycles — fast in-memory checks run every tick while heavier operations like file integrity are spread across frames. The VM adds overhead only to explicitly marked code paths.
EAT collects hardware components (CPU, motherboard, GPU, TPM, etc.) and generates a weighted HWID fingerprint. A BLAKE2b certificate chain signs the license data, stored in a ChaCha20-Poly1305 encrypted vault file. A configurable tolerance threshold allows minor hardware changes without invalidating licenses.
Yes. EAT runs entirely in user mode with no kernel driver. The VM never allocates RWX memory — bytecode is interpreted, not JIT-compiled — so it won't trip anti-cheat systems that flag executable allocations. Process mitigations are applied through the standard Windows API.
Link the EAT SDK and add EAT_INIT() in your entry point. Configure protection with a Lua script or use a built-in preset. EAT.Publish runs as a post-build step — add it to your build events. The cloud dashboard handles license generation and team management from there.

Get in Touch

Product inquiries, licensing questions, or trial requests.

[email protected]

EAT Support

Get instant help from our AI-powered support assistant. Ask about integration, licensing, protection features, or troubleshooting.

Open Support Chat →

Or email [email protected]