jlu-lujing/dsh-studio

C2

★ 0 · jlu-lujing/dsh-studio source on GitHub · this plugin in the registry

jlu-lujing/dsh-studio is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It runs code at install time, executes system commands, decodes base64 payloads, reads credential-class env vars.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
runs code at install timeinstall_scriptpostinstall: node scripts/ensure-spawn-helper.mjs
executes system commandsexec×88 in authored code, e.g. benchmarks/support/built-worker.ts:3, benchmarks/support/built-worker.ts:38
decodes base64 payloadsbase64_decode×3 in authored code, e.g. apps/desktop/scripts/prepare-installed-update-network.ts:47, packages/acp/acp/src/content.ts:55
reads credential-class env varstoken_envCSC_KEYCHAIN, DSH_DESKTOP_WINDOWS_KEY_CONTAINER, DSH_DESKTOP_WINDOWS_TOKEN_PIN

Services it injects

agentDefaultModel agents attachments connection fileReferences fileUpload fileUploads fs llm remote sessionPersistence sessionProjections sessionQuery sessions tools typert typertGateway workspaceRegistry

Hooks it attaches

agent/assistant-stream agent/disposed agent/error agent/inbox/claimed agent/status approval/request connection/request internal/service llm/adapters-updated session/created session/disposed session/event

Outbound domains

download-test.deepseek.com download.deepseek.com harness-test.deepseek.com open.feishu.cn accounts.feishu.cn passport.feishu.cn login.feishu.cn

Environment variables it reads

DSH_DESKTOP_PACKAGING_RUN_DIR npm_execpath DSH_DESKTOP_OPEN_DEVTOOLS SystemRoot DSH_CLIENT_TITLE CORDIS_SHARED DSH_TELEMETRY_DISABLED DSH_HOME ELECTRON_ENABLE_LOGGING DSH_DESKTOP_WINDOWS_CER_FILE

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.