WebAssembly Sandbox Security Simulator
Interactive WebAssembly (WASM) sandbox security simulator: watch a module run inside a bounded linear-memory region and a capability-gated host boundary. Trigger a simulated memory-overflow attempt (stopped at the memory bound) and an unauthorized syscall attempt (stopped because the host never granted that capability).
WebAssembly runs untrusted bytecode at near-native speed, but only inside a strict security model. This simulator visualizes a WASM module executing inside its own bounded linear-memory region, wrapped in a capability-gated sandbox wall. Normal operation writes sequentially into memory pages and calls host functions the module was actually given — imports like console.log and math.sqrt succeed as green beams, drawn from a ring of host capabilities around a central runtime core. Trigger a simulated memory-overflow attempt to see a rogue write trapped exactly at the edge of the linear-memory block, or an unauthorized syscall attempt to see a call to a function outside the import table rejected before it ever reaches the host. Toggle fs.open and net.connect live to see the host grant or revoke a capability, while process.spawn stays permanently locked — a reminder that WASM has no raw system-call instruction at all.
Interactive WebAssembly (WASM) sandbox security simulator: a module runs inside a bounded linear-memory region and a capability-gated host boundary. Normal writes fill memory pages and calls to granted imports (console.log, math.sqrt) succeed as green beams. Trigger a memory-overflow attempt to see a write trapped exactly at the linear-memory bound, and an unauthorized syscall attempt to see a call rejected because the host never granted that capability. Toggle fs.open / net.connect live to grant or revoke a capability; process.spawn stays permanently locked since WASM has no raw syscall instruction.
3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install