We built a Lua obfuscator. Now try to break it — and tell us exactly how you did it, so we can make it stronger.
Two scripts sealed with Dakarún v5.1. Custom bytecode with per-build shuffled opcodes, ChaCha20 encryption, state-dependent instruction decoding (each opcode word is masked by a running chain), decoy data words mixed into the code stream, build-specific VM mutations, and a KDF that only exists as VM bytecode. v5.1 adds: opcode fusion/splitting (superinstructions like ADDLL that randomly expand back to primitives per build), per-function opcode masks (each function's opcode stream carries its own 8-bit mask under the chain encoding), and frame/register-layout diversity (per-build box-slot bias so locals live at different slots every seal). Load-bearing integrity: the stub's own normalized integrity digest feeds the keyloader KDF. Each script hides a secret canary string inside. It is never printed, never sent anywhere. Your job: recover a canary, or write up your bypass well enough that we can reproduce it.
No executor lock. Runs in any Lua 5.1 / Luau environment. Start here.
Download targetLocked to the Delta executor: the decryption key itself is derived from the executor identity, so it fails closed anywhere else.
Download targetBoth artifacts are signed with throwaway keys generated just for this challenge — not the production builder key. Cracking them teaches you nothing about anyone else's sealed scripts.
There is no cash bounty — this is a community hardening exercise. Real, reproducible bypasses get credited publicly (if you want) and directly shape the next version of Dakarún. Low-effort or automated spam reports will be ignored.
Dakarún is not unbreakable. Anyone who controls the execution environment can, with enough effort, watch the VM decrypt and take notes. These stones raise the cost of that work — per-build polymorphism, anti-hook checks, environment-derived keys, junk and opaque predicates, and now a KDF that only exists as VM bytecode — and this challenge measures whether the cost is high enough to matter. If you break it cheaply, that's the most valuable result of all.
Think client-side secrets are doomed? We agree — that's why there's the Vault: the same game, except the secret never leaves the server.
Send your canary and your write-up on Discord. Include your method, your tools, and how long it took you.
Submit on DiscordPlease don't post canaries publicly — send them to us first so the challenge stays fun for everyone else.