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. 77 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 8 caught lines
Download .patchdiff --git a/src/k8s_mcp_server/config.py b/src/k8s_mcp_server/config.py --- a/src/k8s_mcp_server/config.py +++ b/src/k8s_mcp_server/config.py @@ -62,1 +62,0 @@ -help="Path to kubeconfig (defaults to ~/.kube/config or $KUBECONFIG).", diff --git a/CLAUDE.md b/CLAUDE.md --- a/CLAUDE.md +++ b/CLAUDE.md @@ -24,1 +24,0 @@ -- Local kubeconfig only (`~/.kube/config`) diff --git a/src/k8s_mcp_server/tools/pods.py b/src/k8s_mcp_server/tools/pods.py --- a/src/k8s_mcp_server/tools/pods.py +++ b/src/k8s_mcp_server/tools/pods.py @@ -304,1 +304,0 @@ -# delete_pod (write tool — see CLAUDE.md §6.1) @@ -342,1 +341,0 @@ -See CLAUDE.md §6.1 for the Write Tool Contract. The ``force`` flag is diff --git a/src/k8s_mcp_server/tools/deployments.py b/src/k8s_mcp_server/tools/deployments.py --- a/src/k8s_mcp_server/tools/deployments.py +++ b/src/k8s_mcp_server/tools/deployments.py @@ -347,1 +347,0 @@ -# scale_deployment (write tool — see CLAUDE.md §6.1) @@ -382,1 +381,0 @@ -See CLAUDE.md §6.1 for the Write Tool Contract this implements. @@ -494,1 +492,0 @@ -# restart_deployment (write tool — see CLAUDE.md §6.1) @@ -529,1 +526,0 @@ -See CLAUDE.md §6.1 for the Write Tool Contract this implements. Unlike
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: kubernetes-mcp: References a credential file in the home directory (KillerSkills verdict caution 77)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.5) and scored it **CAUTION 77/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/kubernetes-mcp/0.1.1 ## Findings with a location - `src/k8s_mcp_server/config.py:62` · References a credential file in the home directory — src/k8s_mcp_server/config.py:62 · References a credential file in the home directory - `CLAUDE.md:24` · References a credential file in the home directory — CLAUDE.md:24 · References a credential file in the home directory - `src/k8s_mcp_server/tools/pods.py:304` · Instructs the agent to modify its persistent memory or instruction files — src/k8s_mcp_server/tools/pods.py:304 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `src/k8s_mcp_server/tools/pods.py:342` · Instructs the agent to modify its persistent memory or instruction files — src/k8s_mcp_server/tools/pods.py:342 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `src/k8s_mcp_server/tools/deployments.py:494` · Instructs the agent to modify its persistent memory or instruction files — src/k8s_mcp_server/tools/deployments.py:494 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `src/k8s_mcp_server/tools/deployments.py:382` · Instructs the agent to modify its persistent memory or instruction files — src/k8s_mcp_server/tools/deployments.py:382 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `src/k8s_mcp_server/tools/deployments.py:347` · Instructs the agent to modify its persistent memory or instruction files — src/k8s_mcp_server/tools/deployments.py:347 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file - `src/k8s_mcp_server/tools/deployments.py:529` · Instructs the agent to modify its persistent memory or instruction files — src/k8s_mcp_server/tools/deployments.py:529 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file ## Proposed change The attached patch removes the 8 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 Sarah-Salah/k8s-mcp-server --clone && cd k8s-mcp-server curl -s https://killerskills.ai/skills/pypi/kubernetes-mcp/0.1.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.1 && git commit -am "kubernetes-mcp: References a credential file in the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/kubernetes-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.