Skip to content
ThaRealSolomonPublic

About

A privacy-focused Electron/Chromium browser that imports Telegram SOCKS proxies, securely authenticates upstream proxy credentials, and automatically fails over between proxies.

Topics

Resources

Stars

1 star

Watchers

1 watching

Forks

Latest commit

Β 

History

9 Commits

Folders and files

Repository files navigation

Pixel Fox Embracing Telegram Orb

TeleFox

The Chromium browser built around Telegram SOCKS5 proxies.

Import tg://socks proxies, browse through them directly, and automatically fail over when a proxy becomes unavailable.


Download TeleFox Star TeleFox TeleFox Telegram GitHub Issues



Latest Release GitHub Stars Last Commit

⚑ See TeleFox in Action

TeleFox animated demo

🦊 What is TeleFox?

TeleFox is an open-source Electron/Chromium browser designed specifically around Telegram SOCKS5 proxies.

Instead of changing your system proxy or relying on browser extensions, TeleFox provides its own proxy-routing layer so browser traffic can be sent through your selected Telegram SOCKS5 proxy.

Built for

Capability
πŸ”— Import Telegram tg://socks links
πŸ” Support SOCKS5 username/password authentication
🌐 Route Chromium browser traffic through the selected proxy
♻️ Detect failures and perform proxy failover
πŸ—‚οΈ Manage multiple proxy configurations
πŸ”’ Protect stored secrets with Electron safeStorage
🧩 Keep proxy credentials out of the renderer
πŸ“‘ Store and identify tg://proxy MTProto links

πŸš€ Why TeleFox?

Telegram-first proxy workflow

Paste a Telegram SOCKS5 link and use it as a browser proxy without manually configuring Windows or Chromium.

Automatic failover

When an upstream proxy becomes unavailable, TeleFox can detect the failure and use its proxy-selection/failover logic to keep browsing moving.

Native browser routing

Proxy routing happens through Chromium's browser session rather than through a conventional browser extension.

Credential protection

Sensitive proxy credentials are encrypted using Electron's safeStorage and are not exposed to the renderer process.


πŸ” How the SOCKS5 Bridge Works

Chromium does not provide the SOCKS5 username/password authentication workflow required by TeleFox.

TeleFox solves this with a local loopback SOCKS5 bridge:

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚      Chromium        β”‚
β”‚                      β”‚
β”‚   session.setProxy() β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚  127.0.0.1:<random>  β”‚
β”‚    Local SOCKS5      β”‚
β”‚       Bridge         β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β”‚ authenticated
           β–Ό
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Telegram SOCKS5      β”‚
β”‚       Proxy          β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
           β”‚
           β–Ό
        Internet

The local bridge:

  • listens on 127.0.0.1
  • uses a randomly selected local port
  • requires no local authentication
  • authenticates against the configured upstream SOCKS5 proxy
  • forwards browser traffic to the upstream server

Because Chromium connections pass through this bridge, connection failures can also be observed as part of TeleFox's failover mechanism.


πŸ“‘ Telegram Proxy Support

βœ… Browser-capable β€” SOCKS5

tg://socks?server=example.com&port=1080&user=username&pass=password

These proxies can be imported, connected, and used for Chromium browser traffic.

ℹ️ Telegram-only β€” MTProto

tg://proxy?server=example.com&port=443&secret=...

MTProto links are stored and labelled:

Telegram-only / MTProto

They are intentionally prevented from being used as browser proxies because MTProto is not a SOCKS5 browser-proxy protocol.


πŸ›‘οΈ Security

TeleFox is designed so that sensitive proxy credentials stay outside the renderer process.

Passwords and other secrets are protected using:

Electron safeStorage

The browser communicates with the local SOCKS5 bridge, while the bridge handles authentication with the upstream proxy.

This keeps the browser-facing layer separate from upstream proxy credentials.


πŸ“¦ Installation

Requirements

  • Windows
  • Node.js
  • npm

Clone

git clone https://github.com/ThaRealSolomon/TeleFox.git
cd TeleFox

Install dependencies

npm install

Development

Launch TeleFox with DevTools available through F12:

npm run dev

Build

Compile the main and renderer processes:

npm run build

Package for Windows

Create the Windows installer and portable executable:

npm run package

Release artifacts are generated in:

release/

Tests

Run parser, selection, and failover tests:

npm test

🧱 Technology

Technology Role
Electron Desktop application runtime
Chromium Browser engine
TypeScript Application code
SOCKS5 Bridge Authenticated upstream proxy routing
safeStorage Local secret protection
session.setProxy Chromium proxy configuration

πŸ—ΊοΈ Project Architecture

TeleFox
β”‚
β”œβ”€β”€ Electron Main Process
β”‚   β”œβ”€β”€ Proxy management
β”‚   β”œβ”€β”€ SOCKS5 bridge
β”‚   β”œβ”€β”€ Authentication
β”‚   └── Secure storage
β”‚
β”œβ”€β”€ Chromium Renderer
β”‚   └── Browser UI / pages
β”‚
└── Proxy Layer
    β”œβ”€β”€ Telegram SOCKS5
    β”œβ”€β”€ Authentication
    β”œβ”€β”€ Failure detection
    └── Failover

πŸ“₯ Download

Windows x64

Download Latest Release



Portable and installer builds are available from the latest release.


πŸ’¬ Community & Support


🀝 Contributing

Bug reports, technical feedback, improvements, and pull requests are welcome.

For bugs and feature requests:

https://github.com/ThaRealSolomon/TeleFox/issues


⭐ Support the Project

TeleFox is free and open source.

If you find it useful, consider giving the repository a ⭐ on GitHub. It helps more developers discover the project.

Star TeleFox



TeleFox Β· Open Source Β· Electron Β· Chromium Β· Telegram SOCKS5

About

A privacy-focused Electron/Chromium browser that imports Telegram SOCKS proxies, securely authenticates upstream proxy credentials, and automatically fails over between proxies.

Topics

Resources

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages