wqty123/dsh-browser

C3

Shared real browser plugin for DeepSeek Harness

★ 50+ · wqty123/dsh-browser source on GitHub · this plugin in the registry

wqty123/dsh-browser is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes system commands, decodes base64 payloads.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
can rewrite the system promptprompt_surfacesystemPrompt
executes system commandsexec×8 in authored code, e.g. src/browser-electron/remote-host.ts:28, src/browser-electron/remote-host.ts:28
decodes base64 payloadsbase64_decode×2 in authored code, e.g. src/browser-electron/host-main.ts:923, src/browser-electron/provider.ts:2267
starts a network servernet_server×4 in authored code, e.g. desktop-bridge/plugin-browser-bridge.js:335, desktop-bridge/plugin-browser-bridge.js:366
reads credential-class env varstoken_envDSH_BROWSER_RPC_TOKEN

Services it injects

browser locale slots systemPrompt tools

Environment variables it reads

DSH_HOME DSH_BROWSER_RPC_TOKEN XDG_DOWNLOAD_DIR ELECTRON_PATH npm_config_prefix PREFIX DSH_BROWSER_PROBE_RETRY_MS LOCALAPPDATA

How to read this

Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.

Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.