← mcp-for-kibana@0.4.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. 68 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/scripts/experiment/efficiency_report.py b/scripts/experiment/efficiency_report.py --- a/scripts/experiment/efficiency_report.py +++ b/scripts/experiment/efficiency_report.py @@ -794,1 +794,0 @@ -<link href="https://fonts.googleapis.com/css2?family=Newsreader:opsz,[email protected],500;6..72,600&family=Public+Sans:wght@400;600;700&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet"> diff --git a/scripts/experiment/local_report.py b/scripts/experiment/local_report.py --- a/scripts/experiment/local_report.py +++ b/scripts/experiment/local_report.py @@ -317,1 +317,0 @@ -<link href="https://fonts.googleapis.com/css2?family=Newsreader:opsz,[email protected],500;6..72,600&family=Public+Sans:wght@400;600;700&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet"> diff --git a/scripts/experiment/honeycomb_report.py b/scripts/experiment/honeycomb_report.py --- a/scripts/experiment/honeycomb_report.py +++ b/scripts/experiment/honeycomb_report.py @@ -492,1 +492,0 @@ -<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,[email protected],600&family=JetBrains+Mono:wght@400;600&family=Public+Sans:wght@400;600&display=swap"> diff --git a/scripts/experiment/CLAUDE_E2E.md b/scripts/experiment/CLAUDE_E2E.md --- a/scripts/experiment/CLAUDE_E2E.md +++ b/scripts/experiment/CLAUDE_E2E.md @@ -26,1 +26,0 @@ -| Client | Claude Code headless: `claude -p <prompt> --output-format stream-json --verbose --restricted --disable-slash-commands --tools "" --strict-mcp-config --mcp-config <file> --no-session-persist
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.4.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: mcp-for-kibana: URL with embedded credentials (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-for-kibana/0.4.0 ## Findings with a location - `scripts/experiment/efficiency_report.py:794` · URL with embedded credentials — scripts/experiment/efficiency_report.py:794 · URL with embedded credentials — may be phishing or credential leaking - `scripts/experiment/local_report.py:317` · URL with embedded credentials — scripts/experiment/local_report.py:317 · URL with embedded credentials — may be phishing or credential leaking - `scripts/experiment/honeycomb_report.py:492` · URL with embedded credentials — scripts/experiment/honeycomb_report.py:492 · URL with embedded credentials — may be phishing or credential leaking - `scripts/experiment/CLAUDE_E2E.md:26` · Fake instruction boundary tag — scripts/experiment/CLAUDE_E2E.md:26 · Fake instruction boundary tag · informational: not an instruction file · informational: not an instruction file · informational: not an instruction file ## Proposed change The attached patch removes the 4 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 pedro-angel/mcp-for-kibana --clone && cd mcp-for-kibana curl -s https://killerskills.ai/skills/pypi/mcp-for-kibana/0.4.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.4.0 && git commit -am "mcp-for-kibana: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp-for-kibana/0.4.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.