
Browser resource exhaustion payload that crashes target systems via memory, GPU, audio, and rendering overload. Designed for authorized security testing and research.
An analysis and documentation overview of the stress-testing browser script developed by Xer0TLabs & Persephrak Decentralized Syndicate.
WARNING: For educational, research, and authorized testing purposes only. Running this script will immediately freeze or crash the target browser tab, application, or operating system.
This repository contains a comprehensive browser-crashing utility designed to trigger simultaneous hardware and software bottlenecks within modern web browsers. By aggressively targeting the RAM heap, GPU VRAM, audio pipelines, and layout rendering engines, the script creates a catastrophic denial-of-service (DoS) condition on the host machine.
It features targeted optimizations for multiple rendering engines, including Chromium (Blink), Gecko, and WebKit (Safari).
The payload executes a multi-pronged attack across the following vectors:
while(true)preventDefault() touch gesture loops and forced orientation reload cycles to trigger mobile kernel panics.| Engine / Platform | Primary Crash Vector | Expected Outcome |
|---|---|---|
| Chromium (Chrome/Edge) | V8 Engine Heap Exhaustion | "Aw, Snap! Out of Memory" crash screen. |
| Gecko (Firefox) | Rendering Pipeline Freeze | App UI lockup / "Unresponsive Script" warning. |
| Android System | Kernel Low Memory Killer (LMK) | Immediate, silent termination of the browser app. |
| WebKit (Safari / iOS) | Touch Thread Flood & JSC Panic | Complete system lag or forced hardware reboot. |
To analyze the payload, serve the index.html file via a local web server environment (e.g., Python HTTP server, Node.js, Nginx).
DO NOT open this file directly in your primary browser unless you have saved all active work, as it will cause immediate data loss from unresponsiveness.
---
## 5. DISCLAIMER
This software is provided "as-is" without any express or implied warranty. The author(s) assume no liability for system crashes, data corruption, or hardware strain caused by running this script on production or personal devices. Always conduct browser security engineering within a dedicated, isolated sandbox or virtual machine environment.