Web Playground

​

Why Use the Web Version?

​

Enhanced Safety

​

Features

• Full Windows Emulation: Same syscall-level emulation as the desktop version
• Interactive Console: Real-time output and logging
• File Upload: Drag and drop executables and supporting files
• Virtual Filesystem: Browser-based filesystem using IndexedDB
• PE File Analysis: Built-in PE header viewer and icon extraction
• Execution Control: Start, stop, and monitor program execution
• Registry Support: Pre-configured Windows registry

​

Getting Started

​

Web-Specific Features

​

Virtual Filesystem

C:/
├── Windows/
│   ├── System32/       (System DLLs)
│   └── SysWOW64/       (32-bit DLLs on 64-bit)
├── Users/
│   └── User/
│       └── Desktop/    (Upload location)
└── Program Files/

​

File Persistence

1. Click the Settings icon
2. Select “Clear Filesystem”
3. Confirm the action

​

PE File Viewer

• Headers: View DOS, NT, and Optional headers
• Sections: Examine section names, sizes, and characteristics
• Imports: List imported DLLs and functions
• Exports: View exported functions
• Resources: Extract and view resources including icons

​

Icon Extraction

1. Upload an executable
2. The icon appears in the file list
3. Click to view full-size

​

Building the Web Version

​

Prerequisites

• Emscripten SDK
• CMake 3.20+
• Node.js 16+ (for the frontend)

​

Build Steps

​

Architecture

​

WebAssembly Module

• Unicorn Engine (emulation backend)
• Windows syscall implementations
• PE loader and module manager
• Registry and filesystem emulation

​

Web Worker

• Prevent blocking the main UI thread
• Enable SharedArrayBuffer for threading
• Provide better performance

​

Frontend

• React: UI framework
• TypeScript: Type-safe development
• Vite: Build tool and dev server
• Tailwind CSS: Styling
• Radix UI: Accessible components

​

Communication Flow

​

Browser Compatibility

​

Requirements

• WebAssembly: All modern browsers
• SharedArrayBuffer: Required for threading
• IndexedDB: For virtual filesystem persistence

​

Enabling SharedArrayBuffer

Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp

​

Tested Browsers

• ✅ Chrome 90+
• ✅ Firefox 90+
• ✅ Edge 90+
• ✅ Safari 15.2+ (with caveats)
• ❌ Internet Explorer (not supported)

​

Limitations

​

Performance

​

Memory

• Maximum: 2-4GB depending on browser
• Large programs may exceed available memory

​

Network

• Subject to CORS policies
• Cannot make arbitrary TCP/UDP connections
• WebSocket support available

​

File System

• No direct host filesystem access
• Files must be uploaded manually
• Limited total storage (IndexedDB quotas)

​

Debugging

• GDB remote debugging
• External debugger attachment
• Direct memory inspection tools

​

Advanced Usage

​

Embedding in Your Site

import { createEmulator } from './emulator'

const emulator = await createEmulator({
  wasmPath: '/path/to/analyzer.wasm',
  workerPath: '/path/to/emulator-worker.js'
})

// Load executable
await emulator.loadFile('program.exe', executableData)

// Set up callbacks
emulator.onOutput = (text) => console.log(text)
emulator.onExit = (code) => console.log('Exit:', code)

// Run program
await emulator.run(['arg1', 'arg2'])

​

Custom Registry

const registryData = await fetch('/custom-registry.zip')
  .then(r => r.arrayBuffer())

await emulator.loadRegistry(registryData)

​

File Operations

// Write file
await emulator.writeFile('C:/config.ini', configData)

// Read file
const data = await emulator.readFile('C:/output.txt')

// List directory
const files = await emulator.listDirectory('C:/Users/User')

// Delete file
await emulator.deleteFile('C:/temp.dat')

​

Privacy and Security

​

Data Processing

• All processing happens client-side in your browser
• Uploaded files are not sent to any server
• No telemetry or analytics on uploaded executables
• Virtual filesystem is stored locally (IndexedDB)

​

Network Isolation

• Cannot access your local network directly
• Are subject to browser security policies
• Can only make HTTP(S) requests allowed by CORS

​

Clearing Data

1. Clear the virtual filesystem (Settings → Clear Filesystem)
2. Clear browser storage for sogen.dev
3. Close the browser tab

​

Troubleshooting

​

SharedArrayBuffer Errors

1. Ensure you’re using HTTPS (required for security headers)
2. Check that your browser supports SharedArrayBuffer
3. Verify the site’s HTTP headers are correctly configured

​

Out of Memory

1. Close other browser tabs
2. Use a 64-bit browser
3. Try a smaller/simpler executable
4. Use the desktop version for large programs

​

Performance Issues

1. Close unnecessary browser tabs
2. Disable browser extensions
3. Use Chrome or Edge (typically faster WebAssembly)
4. Consider using the desktop version for better performance

​

Files Not Persisting

1. Check browser storage settings
2. Ensure IndexedDB is enabled
3. Verify sufficient storage quota
4. Check for private browsing mode (may not persist)