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. 68 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 3 caught lines
Download .patchdiff --git a/src/mcp_win_stdio/ssh/guide.py b/src/mcp_win_stdio/ssh/guide.py --- a/src/mcp_win_stdio/ssh/guide.py +++ b/src/mcp_win_stdio/ssh/guide.py @@ -20,1 +20,0 @@ -• Auto-Discovery: Automatically reads ~/.ssh/config aliases, identity files & proxy jumps. diff --git a/src/mcp_win_stdio/ssh/server.py b/src/mcp_win_stdio/ssh/server.py --- a/src/mcp_win_stdio/ssh/server.py +++ b/src/mcp_win_stdio/ssh/server.py @@ -266,1 +266,0 @@ -key_path: Path to private key file (e.g. ~/.ssh/id_rsa, C:/Users/.../.ssh/id_ed25519). diff --git a/src/mcp_win_stdio/ssh/connection.py b/src/mcp_win_stdio/ssh/connection.py --- a/src/mcp_win_stdio/ssh/connection.py +++ b/src/mcp_win_stdio/ssh/connection.py @@ -210,1 +210,0 @@ -"""Find default SSH keys in ~/.ssh/ directory."""
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.5. 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: mcp-win-stdio-ssh: Reads credential paths from the home directory (KillerSkills verdict caution 68)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 68/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/mcp-win-stdio-ssh/0.4.5 ## Findings with a location - `src/mcp_win_stdio/ssh/guide.py:20` · Reads credential paths from the home directory — src/mcp_win_stdio/ssh/guide.py:20 · Reads credential paths from the home directory - `src/mcp_win_stdio/ssh/server.py:266` · References a credential file in the home directory — src/mcp_win_stdio/ssh/server.py:266 · References a credential file in the home directory - `src/mcp_win_stdio/ssh/connection.py:210` · Reads credential paths from the home directory — src/mcp_win_stdio/ssh/connection.py:210 · Reads credential paths from the home directory ## 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 indala/mcp-win-stdio --clone && cd mcp-win-stdio curl -s https://killerskills.ai/skills/pypi/mcp-win-stdio-ssh/0.4.5/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.4.5 && git commit -am "mcp-win-stdio-ssh: Reads credential paths from the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp-win-stdio-ssh/0.4.5/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.