THEWOLFWALKER/dsh-notifier
C3Unified notification push plugin for DeepSeek Harness (DSH): one minimal notify() API, 8 channel adapters (telegram/dingtalk/feishu/wxpusher/pushplus/serverchan/bark/webhook), dual trigger (auto sessi
★ 10+ · THEWOLFWALKER/dsh-notifier source on GitHub · this plugin in the registry
THEWOLFWALKER/dsh-notifier is a DeepSeek Harness plugin rated C3 — powerful capability combined with sensitive behavior. It patches the dsh runtime, executes system commands, starts a network server.
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| executes system commands | exec | ×5 src, e.g. scripts/channel-login.mjs:13, scripts/channel-login.mjs:73 |
| starts a network server | net_server | ×3 src, e.g. scripts/hook-server.mjs:7, src/admin/server.mjs:300 |
Services it injects
agents notifier tools
Hooks it attaches
agent/created agent/disposed agent/error approval/request session/event
Outbound domains
oapi.dingtalk.com wxpusher.zjiecode.com www.pushplus.plus qyapi.weixin.qq.com api.chanify.net api.telegram.org api.day.app open.feishu.cn bots.qq.com api.sgroup.qq.com
Environment variables it reads
USERPROFILE PORT OUT DSH_HOME
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.