De*b compiles your Luau scripts into a sealed custom bytecode and runs them inside an embedded virtual machine. It is free, runs fully offline, and its internals have been hardened through repeated adversarial testing against real executor tooling.
OPEN DASHBOARDDe*b turns readable Lua/Luau source into a binary program image understood only by the virtual machine embedded in the output. Instructions never exist as a plain table in memory — each one is unsealed at fetch time under an execution-order key, so recovering the program means reconstructing our machine, not just reading a dump.
for i = 1, 16 do local b = i + (a - 1) * 4 local c, d, e, f = string.byte(msg, b, b + 3) digest[a] = ((c * 256 + d) * 256 + e) * 256 + f end -- after obfuscation, this logic survives only as -- sealed instructions inside a custom register VM
Your script compiles to a custom instruction set and runs inside a register VM baked into the output. There is no plain source and no static instruction table to lift.
Instruction bytes decrypt under a state that evolves in execution order. Static decoding reaches the first instruction only — the rest requires a CFG-walking emulator.
Decryption keys derive partly from a fingerprint of the live runtime environment, so offline byte-level decryption does not work.
Opcode maps, seed keys, operand order, dispatch order and field names are regenerated on every build — signatures from one output do not transfer to the next.
Payloads carry a full-body checksum and runtime gates watch for swapped builtins and tracer hooks, failing closed before anything sensitive is exposed.
The engine's internals were reviewed through the same executor-side techniques used against established obfuscators — memory dumping, interception hooks, registry scans and tracer instrumentation.
Every layer of this engine has been probed the way a real reverse engineer would probe it: dumping live interpreter state, intercepting decoders, scanning the heap for program data, and instrumenting the runtime. Each round of testing tightened the internals — program state now lives and dies inside a single execution frame, serialized data stays sealed at rest, and instrumentation is detected before the sensitive stage is touched.
TRY THE OBFUSCATORNo accounts, no tokens, no upload queue. Obfuscation runs entirely in your browser — your source never leaves your machine. Pair it with the built-in deobfuscation workbench for analysis.
OPEN DASHBOARD