Skip to content

Proxy and requester extension

Jump to bottom
bcoles edited this page Apr 21, 2023 · 3 revisions

Introduction

The proxy and requester extensions are designed to send requests through a victim browser. It tries to use cross origin requests, but will not work unless the target endpoint allows so. Most of the time, only same-origin requests will return responses.

The proxy extension starts a HTTP proxy on port 6789 by default.

Configuration

To enable the two extensions, simply change enable to true in the config.yaml file(s). The files are located in beef root extensions/proxy/config.yaml and extensions/requester/config.yaml

Screenshots

Use a hooked browser as proxy

Forge a request through a hooked browser

User Guide

I. Introduction   |   II. Basic Utilization   |   III. Advanced Utilization   |   IV. Development   |   V. References

Community

Blog   |   Code   |   Youtube   |   Twitter

I - Starting BeEF

  1. Introducing BeEF
  2. Installation
  3. Basics
  4. Troubleshooting

II - Basic Utilization

  1. Configuration
  2. Interface
  3. Information Gathering
  4. Social Engineering
  5. Network Discovery
  6. Metasploit
  7. Tunneling
  8. XSS Rays
  9. Persistence
  10. Creating a Module
  11. Geolocation
  12. Using-BeEF-With-NGROK

III - Advanced Utilization

  1. RESTful API
  2. Autorun Rule Engine
  3. Notifications
  4. Console
  5. WebRTC Extension

IV - Development

  1. Contributing
  2. ActiveRecord
  3. Development Organization
  4. Architecture
  5. BeEF Javascript API
  6. Step By Step Module Creation
  7. Creating a New Extension
  8. BeEF Testing
  9. Browser & OS Compatibility
  10. Database Schema
  11. Development Milestones
  12. Command Module Config
  13. Command Module API

V - References

  1. FAQ
  2. Other
  3. References
  4. Modules
  5. Release Notes
Clone this wiki locally