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. 10 · Blocked
Evidence
- installer lure
Diff · removes 17 caught lines
Download .patchdiff --git a/core/i18n.py b/core/i18n.py
--- a/core/i18n.py
+++ b/core/i18n.py
@@ -24,1 +24,0 @@
-"enter_api_key": "Enter your API Key to authorize",
@@ -55,1 +54,0 @@
-"wants_access": "{client_name} میخواهد به MCP Hub شما دسترسی داشته باشد",
@@ -61,1 +59,0 @@
-"requested_permissions": "دسترسیهای درخواستی:",
@@ -72,1 +69,0 @@
-"security_message": "فقط برنامههایی را که به آنها اعتماد دارید تایید کنید. توکن OAuth دسترسیهای API Key شما را به ارث خواهد برد.",
diff --git a/core/dashboard/routes.py b/core/dashboard/routes.py
--- a/core/dashboard/routes.py
+++ b/core/dashboard/routes.py
@@ -938,1 +938,0 @@
-"projects": "پروژهها",
@@ -940,1 +939,0 @@
-"oauth_clients": "کلاینتهای OAuth",
@@ -941,1 +939,0 @@
-"audit_logs": "لاگهای ممیزی",
@@ -943,1 +940,0 @@
-"services": "سرویسها",
@@ -953,1 +949,0 @@
-"rate_limit_error": "تلاشهای زیاد برای ورود. لطفاً بعداً تلاش کنید.",
diff --git a/core/tool_access.py b/core/tool_access.py
--- a/core/tool_access.py
+++ b/core/tool_access.py
@@ -88,1 +88,0 @@
-"hint_fa": "مشاهده و عیبیابی — بدون تغییر.",
@@ -104,1 +103,0 @@
-"label_fa": "نصبکننده",
@@ -106,1 +104,0 @@
-"hint_fa": "تنظیمات + نصب و فعالسازی پلاگین/قالب از wp.org.",
@@ -222,1 +219,0 @@
-"hint_fa": "مشاهده + راهاندازی/توقف/ریستارت",
@@ -277,1 +273,0 @@
-"hint_fa": "مشاهده محصولات، سفارشها و مشتریان",
diff --git a/tests/test_dashboard.py b/tests/test_dashboard.py
--- a/tests/test_dashboard.py
+++ b/tests/test_dashboard.py
@@ -137,1 +137,0 @@
-assert trans["projects"] == "پروژهها"
diff --git a/core/settings.py b/core/settings.py
--- a/core/settings.py
+++ b/core/settings.py
@@ -38,1 +38,0 @@
-"label_fa": "پلاگینهای فعال",
@@ -46,1 +45,0 @@
-"hint_fa": "حداکثر تعداد سایتهایی که هر کاربر میتواند بسازد",
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.13.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: mcphub-server: installer lure (KillerSkills verdict blocked 10)
## 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 **BLOCKED 10/100**. Summary: no network, touches nothing outside the project, writes no memory. - installer lure Full trace and findings: https://killerskills.ai/skills/pypi/mcphub-server/3.13.1 ## Findings with a location - `core/i18n.py:55` · Hidden zero-width characters detected — core/i18n.py:55 · Hidden zero-width characters detected — may conceal content - `core/dashboard/routes.py:940` · Hidden zero-width characters detected — core/dashboard/routes.py:940 · Hidden zero-width characters detected — may conceal content - `core/i18n.py:24` · Prompting user to enter sensitive credentials — core/i18n.py:24 · Prompting user to enter sensitive credentials — social engineering - `core/i18n.py:61` · Hidden zero-width characters detected — core/i18n.py:61 · Hidden zero-width characters detected — may conceal content - `core/dashboard/routes.py:938` · Hidden zero-width characters detected — core/dashboard/routes.py:938 · Hidden zero-width characters detected — may conceal content - `core/dashboard/routes.py:953` · Hidden zero-width characters detected — core/dashboard/routes.py:953 · Hidden zero-width characters detected — may conceal content - `core/dashboard/routes.py:943` · Hidden zero-width characters detected — core/dashboard/routes.py:943 · Hidden zero-width characters detected — may conceal content - `core/dashboard/routes.py:941` · Hidden zero-width characters detected — core/dashboard/routes.py:941 · Hidden zero-width characters detected — may conceal content - `core/tool_access.py:106` · Hidden zero-width characters detected — core/tool_access.py:106 · Hidden zero-width characters detected — may conceal content - `tests/test_dashboard.py:137` · Hidden zero-width characters detected — tests/test_dashboard.py:137 · Hidden zero-width characters detected — may conceal content - `core/tool_access.py:277` · Hidden zero-width characters detected — core/tool_access.py:277 · Hidden zero-width characters detected — may conceal content - `core/settings.py:38` · Hidden zero-width characters detected — core/settings.py:38 · Hidden zero-width characters detected — may conceal content ## Proposed change The attached patch removes the 17 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 airano-ir/mcphub --clone && cd mcphub curl -s https://killerskills.ai/skills/pypi/mcphub-server/3.13.1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/3.13.1 && git commit -am "mcphub-server: installer lure" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcphub-server/3.13.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.