← ssh-vps-mcp@0.1.1

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. 78 · Caution

Evidence

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

Diff · removes 5 caught lines

Download .patch
diff --git a/vps_mcp/__main__.py b/vps_mcp/__main__.py
--- a/vps_mcp/__main__.py
+++ b/vps_mcp/__main__.py
@@ -30,1 +30,0 @@
-ssh-vps-mcp --host 217.15.166.73 --user root --private-key-path ~/.ssh/id_rsa
@@ -34,1 +33,0 @@
---private-key-path ~/.ssh/id_rsa \\
@@ -49,1 +47,0 @@
-"--private-key-path", "~/.ssh/id_rsa"
@@ -68,1 +65,0 @@
-help="Path to SSH private key file (e.g. ~/.ssh/id_rsa). "
diff --git a/vps_mcp/ssh.py b/vps_mcp/ssh.py
--- a/vps_mcp/ssh.py
+++ b/vps_mcp/ssh.py
@@ -128,1 +128,0 @@
-look_for_keys=False,  # no ~/.ssh/id_rsa fallback

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.1. 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: ssh-vps-mcp: References a credential file in the home directory (KillerSkills verdict caution 78)

## 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 78/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/ssh-vps-mcp/0.1.1

## Findings with a location
- `vps_mcp/__main__.py:30` · References a credential file in the home directory — vps_mcp/__main__.py:30 · References a credential file in the home directory
- `vps_mcp/__main__.py:68` · References a credential file in the home directory — vps_mcp/__main__.py:68 · References a credential file in the home directory
- `vps_mcp/ssh.py:128` · References a credential file in the home directory — vps_mcp/ssh.py:128 · References a credential file in the home directory
- `vps_mcp/__main__.py:34` · References a credential file in the home directory — vps_mcp/__main__.py:34 · References a credential file in the home directory
- `vps_mcp/__main__.py:49` · References a credential file in the home directory — vps_mcp/__main__.py:49 · References a credential file in the home directory

## Proposed change
The attached patch removes the 5 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 aldirrss/vps-mcp --clone && cd vps-mcp
curl -s https://killerskills.ai/skills/pypi/ssh-vps-mcp/0.1.1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.1.1 && git commit -am "ssh-vps-mcp: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/ssh-vps-mcp/0.1.1/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.