# BeEF Manual Testing Plan (Local VM Edition) This document provides a simplified approach for manually testing BeEF modules entirely within the same Linux Ubuntu VM where BeEF is running. ## 1. Environment Setup (Local VM) ### 1.1 BeEF Server 1. **Dependencies**: Already installed via `./install`. 2. **Configuration**: Credentials have been updated in `config.yaml`. 3. **Launch**: Run `./beef` from the repository root. 4. **Access**: Open the local browser (e.g., Firefox) and navigate to the BeEF UI: `http://127.0.0.1:3000/ui/panel`. ### 1.2 Hooked Browsers (Local) For local testing on the same machine: 1. Open a new tab or window in your browser (Firefox, Chromium, etc.). 2. Navigate to the hook demo page: `http://127.0.0.1:3000/demos/butcher/index.html`. 3. The browser will appear in the BeEF "Online Browsers" list as `127.0.0.1`. ## 2. Testing Strategy: Grouped Execution 1. **Phase 1: Common Infrastructure (Firefox)**: Start here. These modules work on the standard Linux/Firefox setup provided by the VM and don't require external devices or specific insecure software. 2. **Phase 2: Specific Requirements (Firefox)**: Test these if you have the specific requirements (e.g., Android device, Flash plugin, specific vulnerable server running). 3. **Phase 3: Other Browsers**: Use Chrome/Edge/Safari for modules that explicitly don't work in Firefox. ## 3. Module Inventory and Instructions ### 3.1 Phase 1: Common Infrastructure (Standard Firefox) Test these modules using **Firefox** on your local Linux VM. They leverage standard browser features or the BeEF infrastructure itself. | Status | Module Name | Instructions / Description | Cleanup Needed | Comments | | :---: | :--- | :--- | :--- | :--- | | [x] | **Alert Dialog** | 1. Set `Title`, `Message`, and `Button name`.
2. Execute module.
3. Verify alert dialog appears on hooked page with configured text. | None. | | | [x] | **BlockUI Modal Dialog** | 1. Set `Message` and `Timeout (s)`.
2. Execute module.
3. Verify blocking overlay appears with message.
4. Wait for timeout or use UnBlockUI to remove. | None. | | | [x] | **Clickjacking** | 1. Set `iFrame Src` to target page for clickjacking.
2. Execute module.
3. Verify page shows overlay for click-based attack.
4. Click as user would to test interaction capture. | None. | | | [x] | **Confirm Close Tab** | 1. Configure: `Confirm text`, `Create a pop-under window on user\`
2. Click Execute.

_Shows a confirm dialog to the user when they try to close a tab._ | Close tab/window. Check for residual pop-unders. | a window pops up, but the text not as per command | | [x] | **Create Foreground iFrame** | 1. Execute module.
2. Click "Our Meaty Friends" button to reveal links.
3. Click any link (e.g., "The Browser Exploitation Framework Project homepage").
4. Verify page loads in fullscreen iFrame overlay (check DevTools for `