Skip to content

Added support for proxying websockets through the victim browser #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nt0xa
Copy link

@nt0xa nt0xa commented Apr 30, 2025

Currently, websockets connections are not proxied through the victim's extension and are handled by the CursedChrome server. The MR implements several new RPC methods to fix this.

Changes:

  • Added new onWebSocketConnection rule to AnyProxy to allow manipulation of WebSocket traffic.
  • Updated the server code to handle WebSocket connections using the new onWebSocketConnection rule and added 2 new RPC methods: WS_MESSAGE and WS_CLOSE.
  • Updated the background script of the extension by adding 3 new RPC methods: WS_CONNECT, WS_MESSAGE and WS_CLOSE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant