LanJinGod/dsh-purge
C3DeepSeek Harness 破甲插件 dsh-purge 1.1.72 — 换包生效、账本自检、三平台分流
★ 50+ · LanJinGod/dsh-purge source on GitHub · this plugin in the registry
LanJinGod/dsh-purge is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, gates tool execution, executes system commands.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt, webServer, system-prompt/assemble, tools/pre-execute |
| gates tool execution | tool_gate | hook: tools/pre-execute |
| executes system commands | exec | ×27 in authored code, e.g. .backup-cwdfix-212947/core.js:5, .backup-cwdfix-212947/core.js:5 |
| base64 decoding in build output only | base64_decode_bundled | ×5 in build output only, e.g. lib/index.js:2598, lib/skills.js:704 |
Tool registrations
59 static tool registration point(s).
lib/index.js:1691tools.registerlib/index.js:1718tools.registerlib/index.js:1780tools.registerlib/redteam/tools.js:407tools.registerlib/redteam/tools.js:436tools.registerlib/redteam/tools.js:469tools.registerlib/redteam/tools.js:485tools.registerlib/redteam/tools.js:728tools.registerlib/redteam/tools.js:783tools.registerlib/redteam/tools.js:868tools.registerlib/redteam/tools.js:894tools.registerlib/redteam/tools.js:926tools.registerlib/redteam/tools.js:942tools.registerlib/redteam/tools.js:953tools.registerlib/redteam/tools.js:977tools.registerlib/redteam/tools.js:999tools.registerlib/redteam/tools.js:1012tools.registerlib/redteam/tools.js:1036tools.registerlib/redteam/tools.js:1062tools.registerlib/redteam/tools.js:1083tools.registerlib/redteam/tools.js:1106tools.registerlib/redteam/tools.js:1132tools.registerlib/redteam/tools.js:1158tools.registerlib/redteam/tools.js:1176tools.registerlib/redteam/tools.js:1190tools.registerlib/redteam/tools.js:1205tools.registerlib/redteam/tools.js:1227tools.registerlib/redteam/tools.js:1241tools.registerlib/redteam/tools.js:1261tools.registerlib/redteam/tools.js:1286tools.registerlib/redteam/tools.js:1309tools.registerlib/redteam/tools.js:1324tools.registerlib/redteam/tools.js:1343tools.registerlib/redteam/tools.js:1369tools.registerlib/redteam/tools.js:1383tools.registerlib/redteam/tools.js:1405tools.registerlib/redteam/tools.js:1426tools.registerlib/redteam/tools.js:1456tools.registerlib/redteam/tools.js:1480tools.registerlib/redteam/tools.js:1493tools.registerlib/redteam/tools.js:1529tools.registerlib/redteam/tools.js:1573tools.registerlib/redteam/tools.js:1594tools.registerlib/redteam/tools.js:1616tools.registerlib/redteam/tools.js:1640tools.registerlib/redteam/tools.js:1676tools.registerlib/redteam/tools.js:1687tools.registerlib/redteam/tools.js:1711tools.registerlib/redteam/tools.js:1726tools.registerlib/redteam/tools.js:1745tools.registerlib/redteam/tools.js:1774tools.registerlib/redteam/tools.js:1795tools.registerlib/redteam/tools.js:1812tools.registerlib/redteam/tools.js:1871tools.registerlib/redteam/tools.js:1886tools.registerlib/redteam/tools.js:1937tools.registerlib/redteam/tools.js:1955tools.registerlib/redteam/tools.js:1978tools.registerlib/redteam/tools.js:1995tools.register
Services it injects
locale redteam slots systemPrompt tools webServer
Hooks it attaches
agent-preset/selected agent/inbox/claimed agent/pre-step agent/request session/created session/event subagent/end system-prompt/assemble tools/post-execute tools/pre-execute
Outbound domains
codeload.github.com fofa.info oa.example.com oa.demo.com api.github.com
Environment variables it reads
DSH_HOME DSH_PERMISSION_MODE TEMP LOCALAPPDATA DSH_DESKTOP_INSTALL DSH_BASE DSH_SYSTEM_PROMPT APPDATA DSH_PROFILE SystemRoot
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.