Xs1KVerOA/dsh-plugin
C3dsh plugin repo
★ 0 · Xs1KVerOA/dsh-plugin source on GitHub · this plugin in the registry
Xs1KVerOA/dsh-plugin is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can intercept API traffic, executes system commands, decodes base64 payloads.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can intercept API traffic | api_intercept | apiProxy, webServer |
| executes system commands | exec | ×6 in authored code, e.g. dsh-security/audit-tools.js:1, dsh-security/audit-tools.js:70 |
| decodes base64 payloads | base64_decode | ×6 in authored code, e.g. resource-center-plugin/client.js:1575, resource-center-plugin/client.js:1620 |
| starts a network server | net_server | ×1 in authored code, e.g. resource-center-plugin/service-manager-host.js:452 |
| reads credential-class env vars | token_env | DSH_RESOURCE_CENTER_MINIO_ACCESS_KEY, DSH_RESOURCE_CENTER_MINIO_SECRET_KEY, DSH_RESOURCE_CENTER_MINIO_TOKEN |
Tool registrations
36 confirmed registration point(s); analysis is incomplete.
dsh-security/audit-tools.js:124tools.registerdsh-security/audit-tools.js:124tool factorydsh-security/audit-tools.js:138tools.registerdsh-security/audit-tools.js:138tool factorydsh-security/audit-tools.js:147tools.registerdsh-security/audit-tools.js:147tool factorydsh-security/audit-tools.js:156tools.registerdsh-security/audit-tools.js:156tool factorydsh-security/audit-tools.js:165tools.registerdsh-security/audit-tools.js:165tool factorydsh-security/audit-tools.js:174tools.registerdsh-security/audit-tools.js:174tool factorydsh-security/audit-tools.js:183tools.registerdsh-security/audit-tools.js:183tool factorydsh-security/audit-tools.js:190tools.registerdsh-security/audit-tools.js:190tool factorydsh-security/tools.js:14tools.registerdsh-security/tools.js:14tool factorydsh-security/tools.js:26tools.registerdsh-security/tools.js:26tool factorydsh-security/tools.js:33tools.registerdsh-security/tools.js:33tool factorydsh-security/tools.js:40tools.registerdsh-security/tools.js:40tool factorydsh-security/tools.js:47tools.registerdsh-security/tools.js:47tool factorydsh-security/tools.js:54tools.registerdsh-security/tools.js:54tool factorydsh-security/tools.js:61tools.registerdsh-security/tools.js:61tool factoryresource-center-plugin/service-manager-host.js:1572tools.registerresource-center-plugin/service-manager-host.js:1572tool factoryresource-center-plugin/test-host.js:1451tools.registerresource-center-plugin/test-host.js:1451tool factoryresource-center-plugin/test-host.js:1471tools.registerresource-center-plugin/test-host.js:1471tool factorydsh-security/index.js:1458Cannot establish the tools service bindingresource-center-plugin/right-sidebar-host.js:534Cannot establish the tools service bindingresource-center-plugin/right-sidebar-host.js:1623Cannot establish the tools service bindingresource-center-plugin/right-sidebar-host.js:2684Cannot establish the tools service bindingresource-center-plugin/right-sidebar-host.js:2726Cannot establish the tools service bindingresource-center-plugin/right-sidebar-host.js:2764Cannot establish the tools service binding
1 source file(s) omitted by size/count/encoding limits; tool count is incomplete
Services it injects
agentPresets apiProxy connection credentials dshAuth dshSecurity fs inputTriggers llm locale remote sandboxPolicy sessionQuery sessions slots storage storageDomain timer tools webRuntime webServer workspaces
Hooks it attaches
llm/stream session/created session/event
Outbound domains
minio.example.com hunter.qianxin.com
Environment variables it reads
DSH_HOME DSH_CORE_ROOT DSH_DEX_USER_ROOT DSH_RESOURCE_CENTER_MINIO_ENDPOINT DSH_RESOURCE_CENTER_MINIO_ACCESS_KEY DSH_RESOURCE_CENTER_MINIO_SECRET_KEY DSH_RESOURCE_CENTER_MINIO_REGION DSH_RESOURCE_CENTER_MINIO_BUCKET DSH_RESOURCE_CENTER_MINIO_TOKEN
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.