sol5766/dshm

C3

deepseek harnes HarmonyOS PC client

★ 50+ · sol5766/dshm source on GitHub · this plugin in the registry

sol5766/dshm is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It can rewrite the system prompt, executes system commands, uses eval / new Function, decodes base64 payloads.

Not installable — declares only dsh.client, which dsh plugin add cannot install

What it can do

CapabilityFlagEvidence
can rewrite the system promptprompt_surfacesystemPrompt
executes system commandsexec×114 in authored code, e.g. tools/assert-fs-search-fallback.mjs:17, tools/assert-fs-search-fallback.mjs:17
uses eval / new Functioneval×4 in authored code, e.g. tools/assert-fs-search-fallback.mjs:187, tools/check-ptc-runtime-inproc.mjs:766
decodes base64 payloadsbase64_decode×5 in authored code, e.g. tools/pack-core.mjs:587, hostkit/src/core/crypto.mjs:74
starts a network servernet_server×14 in authored code, e.g. tools/assert-report9-fixes.mjs:82, tools/assert-report9-fixes.mjs:98
reads credential-class env varstoken_envDEEPSEEK_API_KEY, DSHM_TEST_KEY, DSH_PROBE_TOKEN

Tool registrations

6 confirmed registration point(s); analysis is incomplete.

1 source file(s) omitted by size/count/encoding limits; tool count is incomplete

Services it injects

documentPreviews fs locale sandboxPolicy slots systemPrompt tools workspaceRegistry

Outbound domains

api.bilibili.com codeload.github.com www.bilibili.com evil.com registry.npmmirror.com gitcode.com gitlab.com ghfast.top 127.0.0.1.evil.com gh-proxy.com

Environment variables it reads

DSHM_PUBLIC_DOWNLOAD DSHM_SANDBOX_HOME DSHM_PROFILE_PNPM_BRIDGE DSHM_HOME JAVA_HOME DSH_VERSION DEVECO_CLI_CLT_PATH DEVECO_SDK_HOME OHOS_SDK_HOME DSHM_CHECK_PORT

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.