SOCKS5 proxy tool that uses Azure Storage services as a means of communication.
SOCKS5 proxy tool that uses Azure Storage services as a means of communication.
New release ! see CHANGELOG
SOCKS proxy over Azure Storage service
ProxyBlob is a tool designed to create SOCKS proxy tunnels through Azure Storage services. This is particularly useful in environments where direct network connectivity is restricted but *.core.windows.net is accessible.
The system consists of two components:
In order to use ProxyBlob, you will need an Azure Subscription to create an Azure Storage Account. Once you have a subscription, you can create a storage account in the Azure Portal or using the Azure CLI.
Here are the steps to create a storage account using the Azure Portal:
Storage account settings:
Once the deployment is complete, you will see the newly created storage account in the list.
Finally, click on "Security + networking" and then "Access keys" to get the storage account key.
Here are the steps to create a storage account using the Azure CLI:
# Login to Azure
az login
# Create a resource group
az group create --name "proxyblob-resource-group" --location "Central US"
# Create a storage account
az storage account create --name "myproxyblob" --resource-group "proxyblob-resource-group" --location "Central US" --sku "Premium_LRS" --kind BlockBlobStorage
# Get the storage account key
az storage account keys list --account-name "myproxyblob" --output tableYou should see displayed the storage account keys.
If you want to test the tool, you can also use Azurite, a lightweight server clone of Azure Storage that can be run locally. To install Azurite, I recommend using either Visual Studio Code extension or Docker.
For the extension, installation is straightforward:
Azurite.azuriteYou should see down right of your editor 3 buttons like this:
[Azurite Table Service] [Azurie Queue Service] [Azurite Blob Service]Press on the [Azurite Blob Service] and the service should be running.
For Docker, you will have to pull the image and run it:
docker pull mcr.microsoft.com/azure-storage/azurite
docker run -p 10000:10000 mcr.microsoft.com/azure-storage/azuriteThe default storage account name is devstoreaccount1 and the account key is Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==.
# Clone the repository
git clone https://github.com/quarkslab/proxyblob
cd proxyblob
# Build all components
makeThis will produce the following binaries:
proxy - the proxy server running on your machineagent - the agent running on the targetagent.wasm - the agent compiled for WebAssemblyThe WASM agent requires the JS host runtime to expose two global functions:
// Open a TCP connection to host:port, call callbacks on events
TCPDial(host, port, onConnect, onData, onClose, onError)
// Bind a UDP socket on a random port, call callbacks on events
UDPListen(onBind, onData, onError)The runner is responsible for implementing these using the runtime's native APIs (e.g. Bun: Bun.connect / Bun.udpSocket, Node.js: net / dgram).
You can also build targets individually:
make proxy # proxy server only
make agent # native agent only
make wasm # WASM agent only
make agent TOKEN= # native agent with embedded connection string
make wasm TOKEN= # WASM agent with embedded connection stringCreate a config.json file based on the example with your Azure Storage credentials:
{
"listeners": [
{
"name": "blob-listener",
"driver": "azblob",
"address": "https://proxyblob.blob.core.windows.net",
"storage_account": "proxyblob",
"storage_account_key": "your_account_key"
},
{
"name": "queue-listener",
"driver": "azqueue",
"address": "http://127.0.0.1:10001",
"storage_account": "devstoreaccount1",
"storage_account_key": "Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw=="
}
]
}
You can configure multiple listeners and manage them in the proxy CLI.
./proxy -c my-config.json # if omitted, config.json is used by defaultThis will start an interactive CLI with the following commands:
Commands:
agent manage agents
clear clear the screen
exit exit the shell
help use 'help [command]' for command help
listener manage listeners
new generate a new connection string for an agentOnce the proxy server is running, start a listener. The started listener automatically becomes the default for subsequent commands.
proxyblob » listener start blob-local-listener
21:23:25 INF Aznet listener started and set as default addr=http://127.0.0.1:10000 driver=azblob listener_id=blob-local-listenerThen you can generate a connection string by using the new command.
…Use the generated connection string with the agent (see below Starting the Agent). If the agent connects successfully, you should see its identity (user@host) in the "Info" column when you list agents.
…Select the agent using agent select and start the proxy listener (by default it listens on localhost:1080) by using the agent start command.
proxyblob » agent select 7b5af883-7cc7-45a4-8599-da906753005d
22:10:40 INF Agent selected agent_id=7b5af883-7cc7-45a4-8599-da906753005d
7b5af883 » agent start
22:10:46 INF Proxy started agent_id=7b5af883-7cc7-45a4-8599-da906753005d port=1080You can now use for example proxychains to tunnel the traffic through the SOCKS proxy.
proxychains xfreerdp /v:dc01.domain.local /u:AdministratorIn order to run, the agent requires a connection string that can be generated using the proxy. You can pass it as an argument or directly embed it at compile-time.
# Via argument
./agent -c
# Build the agent with embedded connection string
make agent TOKEN=
./agentThe communication flow works like this:
The global flow is the following:
…An example of a CONNECT operation is the following:
…Why does my agent immediately stop running ?
There might be several reasons why your agent stops immediately after you run it. Check its exit code:
# Bash
echo $?REM CMD
echo %ERRORLEVEL%# PowerShell
echo $LastExitCodeEach exit code describes why the agent stopped running:
| Exit code | Reason |
|---|---|
| 0 | No error |
| 1 | The context has been canceled |
| 2 | The connection string is missing |
| 3 | The connection string is invalid or expired |
If you encounter issues:
ProxyBlob v2.2 - 03/08/2026:
azure-sdk-for-go submodule; the WASM fix it carried is now upstream (Azure/azure-sdk-for-go#26748)git clone is enough to buildProxyBlob v2.1 (WASM agent) - 19/03/2026:
agent.wasm) for deployment in JavaScript runtimes (Bun, Node.js, etc.)ProxyBlob v2 (aznet boosted) - 16/02/2026:
ProxyBlob public release - 29/04/2025:
Made with ❤️ by @_atsika
No open issues yet, or sync has not completed.