🕷️ HAD Proxy Commander + Cookie Vault

Proxy Management & Cookie Manipulation — All in One Chrome Extension

---

📸 Preview

---

📖 Overview

HAD is a powerful browser extension that combines proxy management with a full-featured cookie editor. Built for penetration testers, developers, and privacy enthusiasts who need granular control over their browser's network traffic and cookie data.

🎯 Key Features

• ⚡ Proxy Commander — Quickly switch between HTTP, HTTPS, SOCKS4 & SOCKS5 proxies
• 🍪 Cookie Vault — View, edit, delete, and export cookies per domain
• 🔐 Auto-Restore — Persist proxy settings across browser sessions
• 📋 Export/Import — JSON, Netscape (.txt), and Header string formats
• 🏃 Bypass List — Define hosts that bypass the proxy
• 🔍 Proxy Tester — Ping your proxy server to verify connectivity
• 🎨 Dark UI — Cyberpunk-themed interface optimized for low-light work

---

🚀 Installation

📦 Google Chrome (Chromium-based)

Method 1: Developer Mode (Manual)

1. Download or clone this repository:

   git clone https://github.com/batmanpriv/proxy-cookie.git

2. Open Chrome and navigate to chrome://extensions/
3. Enable "Developer mode" (toggle in top-right corner)
4. Click "Load unpacked"
5. Select the folder containing the extension files (manifest.json, background.js, etc.)
6. The extension icon (🕷️) will appear in the toolbar

Method 2: CRX Package (Not Recommended)

⚠️ This method is deprecated by Google. Use Developer Mode instead.

Method 3: Chrome Web Store (When Published)

1. Visit the Chrome Web Store listing
2. Click "Add to Chrome"
3. Confirm the installation

---

🦊 Mozilla Firefox

Firefox extensions are signed, but you can install unpacked versions via about:debugging.

Method 1: Temporary Installation (Development)

1. Open Firefox and navigate to about:debugging#/runtime/this-firefox
2. Click "Load Temporary Add-on"
3. Navigate to the extension folder and select any file (e.g., manifest.json)
4. The extension will load temporarily (removes on browser restart)

Method 2: Build a Signed XPI (For Permanent Use)

1. Zip the extension files:

   zip -r had-proxy-cookie.xpi background.js had.png manifest.json popup.html popup.js

2. Submit the XPI to Mozilla Add-on Developer Hub
3. Follow their signing process
4. Once signed, install the .xpi file directly in Firefox

Note: Firefox requires explicit permission grants. You'll see a prompt on first use.

---

🧩 Files Structure

├── background.js          # Service worker — Proxy logic, storage, messaging
├── had.png                # Extension icon
├── manifest.json          # Manifest V3 configuration
├── popup.html             # Popup interface (HTML)
└── popup.js               # Popup logic — UI controls, cookie operations

---

🧠 How It Works

Proxy Engine

• Uses Chrome's proxy.settings API to dynamically change network routes
• Supports fixed_servers mode with custom bypass lists
• Stores and persists settings via chrome.storage.local
• On browser restart, auto-restores if autoRestore is enabled

Cookie Manager

• Fetches all cookies for the current active tab's domain
• Provides full CRUD operations:
  • Create via import (JSON, Netscape, Header)
  • Read with live search
  • Update with inline editor
  • Delete individual or all cookies

Export Formats

Format	Use Case
Header	Copy-paste into Cookie header for cURL/requests
JSON	Programmatic use, backup
Netscape	Compatible with curl -b cookies.txt and other tools

---

🎮 Usage Guide

Setting Up a Proxy

1. Click the 🕷️ extension icon
2. In the Proxy tab:
   • Select protocol: HTTP, HTTPS, SOCKS4, or SOCKS5
   • Enter host (e.g., 127.0.0.1) and port (e.g., 8085)
3. Click 🔍 TEST to verify connectivity
4. Click ⚡ ACTIVATE to enable the proxy
5. The status bar turns RED when active

Managing Cookies

1. Navigate to the Cookies tab
2. All cookies for the current domain appear automatically
3. Use the search bar to filter by name or value
4. Actions per cookie:
   • ✏️ EDIT — Change the value inline
   • 🗑️ DEL — Delete the cookie
   • 📋 COPY — Copy as name=value
5. Bulk actions:
   • REFRESH — Reload cookie list
   • COPY — Copy all cookies in selected format
   • CLEAR ALL — Delete all cookies for the domain
6. Export/Import:
   • Select format (Header / JSON / Netscape)
   • EXPORT → Downloads as file
   • IMPORT → Paste raw data and apply

Bypass List

• Found in the Config tab
• Hosts listed here will not use the proxy
• Defaults: localhost, 127.0.0.1, ::1
• One domain per line

Auto-Restore

• Toggle in Config tab
• When enabled, the proxy is reactivated every time the browser starts

---

🛠️ Technical Details

Permissions (manifest.json)

Permission	Reason
proxy	Control browser proxy settings
storage	Persist user preferences
cookies	Read/write cookies
activeTab	Access current tab's domain
scripting	Inject content scripts (if needed)

API Usage

API	Purpose
chrome.proxy.settings.set()	Enable proxy
chrome.proxy.settings.clear()	Disable proxy
chrome.cookies.getAll()	Retrieve all cookies
chrome.cookies.set()	Create/update cookie
chrome.cookies.remove()	Delete cookie
chrome.storage.local	Persistent storage
chrome.runtime.onMessage	Communication between popup & service worker

Communication Flow

popup.js (UI) 
    ↓ chrome.runtime.sendMessage()
background.js (Service Worker)
    ↓ Chrome APIs (proxy, cookies, storage)
response via sendResponse() → popup.js updates UI

---

🔐 Security Considerations

• No external tracking — All data stays local to your browser
• Cookie data is never transmitted or logged externally
• Proxy credentials are not stored (you can modify background.js to add auth if needed)
• Bypass list prevents sensitive internal traffic from being proxied

---

🐛 Troubleshooting

Proxy Not Working?

• Ensure the proxy server is running
• Check the host/port and protocol
• Disable other proxy extensions
• Try adding your target domain to the bypass list (if you don't want it proxied)

Cookies Not Showing?

• Refresh the page manually (F5)
• Click the REFRESH button in the extension
• Ensure you're on the correct domain

"Load Unpacked" Fails?

• Verify manifest.json is present in the root
• Check for syntax errors in the JSON
• Make sure all files are in the same folder

Firefox Compatibility

• chrome.* APIs are partially supported via WebExtensions polyfill
• For production, use the webextension-polyfill library