🔬 UAF Demo — Real WebAssembly Memory

Uses WebAssembly.Memory — actual OS-backed memory pages allocated by Chrome

✅ REAL MEMORY ADDRESSES
📦 WebAssembly Linear Memory — Raw Hex Dump (real bytes at real offsets)
Magic/Header
String Data
vtable Pointer
Freed / Garbage
Attacker Data
Fake vtable
🔗 Pointer State
fontPtr = uninitialized
newObjPtr = —
⚡ vtable Call Result
vtable ptr: —
🧬 Struct Inspector — 0x???? (48 bytes)
+0x00 magic — 4B
+0x04 name[32] — 32B
+0x24 value — 4B
+0x28 vtable_ptr — 4B ⚠️
+0x2C refcount — 4B
📋 Memory Event Log
00:00 WebAssembly.Memory initialized (64 KB = 1 page). Ready.
Body
CSS Hack Demo
See how a browser gets tricked through a memory bug

Memory is like a hotel. A browser books a room, uses it, checks out — but keeps the key. A hacker moves into that room. The old key still opens it. 💥

🟢 Book → 🔴 Check out → 🟡 New guest → 🟠 Old key works!
✅ Safe simulation. No real hacking involved.