vHack API Viewer

A local tool for viewing vHack Revolutions API requests & responses in a readable format.

Observer proxy (already decrypted with a clean UI).

What is displayed

Direction	Meaning
C2S	Client → Server (request)
S2C	Server → Client (response)

Each packet is displayed as a plain text command, for example:

:SCAN::...
:EXPLOIT::...
:CONNECTIONS:...

How to run

1. Install Node.js 18+

2. Start the viewer

cd vhack-api-viewer
node server.js

Default:

• TCP Proxy: 127.0.0.1:8182
• Web UI: http://127.0.0.1:8787
• Target server: vhack.cc:8182

Other options:

node server.js --host 0.0.0.0 --port 8182 --ui 8787
# if decryption fails (key changed):
node server.js --key "new_aes_key"

3. Route game traffic to the proxy

The game connects to vhack.cc:8182. To route it through this tool, use one of these methods:

Option A — edit hosts + local port (most common on Windows)

1. Start the viewer first (node server.js).
2. Redirect the game hostname to your PC, for example in C:\Windows\System32\drivers\etc\hosts:

127.0.0.1 vhack.cc

3. Make sure the proxy listens on port 8182 (default).
4. Open the game → traffic enters the viewer.
5. Important: after finishing analysis, remove that hosts line so the connection returns to normal.

Note: if the game resolves the IP directly (not the hostname), uses certificate pinning, or connects another way, hosts alone may not be enough. In that case, you need firewall-level redirection, Proxifier, etc.

Option B — Proxifier / similar

Rule: application vhack_rev.exe → proxy/chain to 127.0.0.1:8182 (raw TCP, not an HTTP proxy).

4. Open the UI

Open: http://127.0.0.1:8787

• Left: live packet stream
• Right: plain text details + params (::) + nearest request/response pair
• Filter by direction / command / keyword
• Export JSON for saving

Short technical flow

Game Client  --TCP-->  API Viewer proxy (:8182)  --TCP-->  vhack.cc:8182
                              |
                              +--> decrypt AES (C2S)
                              +--> parse :COMMAND:
                              +--> displayed in the browser UI

• Client packets are usually AES-256-CBC (JSON {data, checksum}).
• Many server packets are plain :COMMAND: ... separated by \r\n.
• The proxy forwards the original bytes to the server/client (does not change gameplay).

Troubleshooting

Symptom	Try
UI empty, no packets	Game is not going through the proxy yet; check hosts/Proxifier
Packets appear but plaintext is garbled/error	AES key outdated → find a new key / --key
Game does not connect	Port 8182 is in use; close other apps; check firewall
Hosts is confusing	Remove 127.0.0.1 vhack.cc after finishing

Ethics & risk

• For learning the protocol / debugging the client on your own account.
• Do not use it for bots, API spam, or violating vHack ToS.
• The key/protocol may change with any game update.