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. 72 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 5 caught lines
Download .patchdiff --git a/src/vestibule/backends/native_helper.py b/src/vestibule/backends/native_helper.py
--- a/src/vestibule/backends/native_helper.py
+++ b/src/vestibule/backends/native_helper.py
@@ -4,1 +4,0 @@
-`vestibule-warden -S -P -c "exec(open(<fd>,'rb').read())"`, and this file is that program
diff --git a/src/vestibule/backends/native.py b/src/vestibule/backends/native.py
--- a/src/vestibule/backends/native.py
+++ b/src/vestibule/backends/native.py
@@ -182,1 +182,0 @@
-"vestibule-warden", "-S", "-P", "-c", f"exec(open({source},'rb').read())",
diff --git a/src/vestibule/backends/select.py b/src/vestibule/backends/select.py
--- a/src/vestibule/backends/select.py
+++ b/src/vestibule/backends/select.py
@@ -775,1 +775,0 @@
-~/.docker/config.json puts those two words in a WARNING on the first line instead. It doesn't
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -9,1 +9,0 @@
-Terminal recording. A short program runs twice. On the machine itself it reads a fake key file and connects to 1.1.1.1. Run through Vestibule, the same program
diff --git a/PYPI.md b/PYPI.md
--- a/PYPI.md
+++ b/PYPI.md
@@ -9,1 +9,0 @@
-Terminal recording. A short program runs twice. On the machine itself it reads a fake key file and connects to 1.1.1.1. Run through Vestibule, the same program
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.2. 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: vestibule-mcp: Python exec or eval of computed code (KillerSkills verdict caution 72)
## 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 72/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/vestibule-mcp/0.1.2 ## Findings with a location - `src/vestibule/backends/native_helper.py:4` · Python exec or eval of computed code — src/vestibule/backends/native_helper.py:4 · Python exec or eval of computed code - `src/vestibule/backends/native.py:182` · Python exec or eval of computed code — src/vestibule/backends/native.py:182 · Python exec or eval of computed code - `src/vestibule/backends/select.py:775` · References a credential file in the home directory — src/vestibule/backends/select.py:775 · References a credential file in the home directory - `README.md:9` · Image alt text carrying instructions — README.md:9 · Image alt text carrying instructions - `PYPI.md:9` · Image alt text carrying instructions — PYPI.md:9 · Image alt text carrying instructions ## 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 victorperson999/Vestibule --clone && cd Vestibule curl -s https://killerskills.ai/skills/pypi/vestibule-mcp/0.1.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.2 && git commit -am "vestibule-mcp: Python exec or eval of computed code" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/vestibule-mcp/0.1.2/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.