← dsh-immune-system@2.3.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 72 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 3 caught lines

Download .patch
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -97,1 +97,0 @@
-<summary><b>Native DSH &amp; ZCode install details + manual MCP JSON</b></summary> **DeepSeek Harness (DSH)**: ```bash dsh plugin --profile <profile> add dsh-im
@@ -220,1 +219,0 @@
-immune sync-doc                    # update <!-- immune:generated --> block in AGENTS.md or CLAUDE.md
diff --git a/README.zh-CN.md b/README.zh-CN.md
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -263,1 +263,0 @@
-<summary><b>展开查看全部 21 项 MCP Server 工具</b></summary> | MCP 工具名 | 功能说明 | | --- | --- | | `immune_match` | 针对当前任务检索匹配抗体并记录投递回执 | | `immune_list` | 只读浏览抗体库(绝不虚增命中计数

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.3.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: dsh-immune-system: Instructs the agent to modify its persistent memory or instruction files (KillerSkills verdict caution 72)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 72/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/dsh-immune-system/2.3.0

## Findings with a location
- `README.md:220` · Instructs the agent to modify its persistent memory or instruction files — README.md:220 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `README.md:97` · Collapsed <details> block carrying instructions — README.md:97 · Collapsed <details> block carrying instructions
- `README.zh-CN.md:263` · Collapsed <details> block carrying instructions — README.zh-CN.md:263 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 3 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._
# or from a terminal, under your own account:
gh repo fork meat-daemon-404/agent-immune --clone && cd agent-immune
curl -s https://killerskills.ai/skills/npm/dsh-immune-system/2.3.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.3.0 && git commit -am "dsh-immune-system: Instructs the agent to modify its persistent memory or instruction files"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/dsh-immune-system/2.3.0/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.