← zeus-dev-helper-mcp@0.7.13

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 20 caught lines

Download .patch
diff --git a/src/zeus_dev_helper_mcp/first_create.py b/src/zeus_dev_helper_mcp/first_create.py
--- a/src/zeus_dev_helper_mcp/first_create.py
+++ b/src/zeus_dev_helper_mcp/first_create.py
@@ -36,1 +36,0 @@
-"Do not type the password into this form."
@@ -40,1 +39,0 @@
-"Do not type the API key into this form. "
@@ -46,1 +44,0 @@
-"Do not type the password into this form."
@@ -53,1 +50,0 @@
-"Put COUCHBASE_PASSWORD in the app .env. Do not type the password into this form."
@@ -58,1 +54,0 @@
-"Put COUCHBASE_PASSWORD in the app .env. Do not type the password into this form."
diff --git a/src/zeus_dev_helper_mcp/clarify.py b/src/zeus_dev_helper_mcp/clarify.py
--- a/src/zeus_dev_helper_mcp/clarify.py
+++ b/src/zeus_dev_helper_mcp/clarify.py
@@ -90,1 +90,0 @@
-"Do not type the password into this form. "
diff --git a/src/zeus_dev_helper_mcp/beer.py b/src/zeus_dev_helper_mcp/beer.py
--- a/src/zeus_dev_helper_mcp/beer.py
+++ b/src/zeus_dev_helper_mcp/beer.py
@@ -1248,1 +1248,0 @@
-<link href="https://fonts.googleapis.com/css2?family=Fraunces:opsz,[email protected],500;9..144,600&family=Outfit:wght@400;500;600&display=swap" rel="stylesheet" />
@@ -1891,1 +1890,0 @@
-`config.json` `llm.api_key_env` stays the name `LLM_API_KEY`. Do not paste
diff --git a/src/zeus_dev_helper_mcp/llm_key.py b/src/zeus_dev_helper_mcp/llm_key.py
--- a/src/zeus_dev_helper_mcp/llm_key.py
+++ b/src/zeus_dev_helper_mcp/llm_key.py
@@ -178,1 +178,0 @@
-"Do not paste the secret into config.json. "
@@ -248,1 +247,0 @@
-"Do not paste the secret into api_key_env. "
diff --git a/src/zeus_dev_helper_mcp/scaffold.py b/src/zeus_dev_helper_mcp/scaffold.py
--- a/src/zeus_dev_helper_mcp/scaffold.py
+++ b/src/zeus_dev_helper_mcp/scaffold.py
@@ -797,1 +797,0 @@
-`config.json` `llm.api_key_env` stays the name `LLM_API_KEY`. Do not paste the secret there.
@@ -883,1 +882,0 @@
-`config.json` `llm.api_key_env` stays the name `LLM_API_KEY`. Do not paste the secret there.
@@ -984,1 +982,0 @@
-"Never pass secret values into MCP tools — set_prereq uses presence flags only."
diff --git a/src/zeus_dev_helper_mcp/prompts.py b/src/zeus_dev_helper_mcp/prompts.py
--- a/src/zeus_dev_helper_mcp/prompts.py
+++ b/src/zeus_dev_helper_mcp/prompts.py
@@ -40,1 +40,0 @@
-… (or the name in config.json). llm.api_key_env stays that variable name. Do not paste the secret into api_key_env. Then smoke_test_zeus. Lists can render before an LLM key exis…
diff --git a/src/zeus_dev_helper_mcp/server.py b/src/zeus_dev_helper_mcp/server.py
--- a/src/zeus_dev_helper_mcp/server.py
+++ b/src/zeus_dev_helper_mcp/server.py
@@ -259,1 +259,0 @@
-"The card names the app .env. Put ZEUS_PASSWORD there. Do not type the password "
diff --git a/src/zeus_dev_helper_mcp/yelp.py b/src/zeus_dev_helper_mcp/yelp.py
--- a/src/zeus_dev_helper_mcp/yelp.py
+++ b/src/zeus_dev_helper_mcp/yelp.py
@@ -651,1 +651,0 @@
-"Do not type the password into the form."
diff --git a/tests/test_clarify.py b/tests/test_clarify.py
--- a/tests/test_clarify.py
+++ b/tests/test_clarify.py
@@ -32,1 +32,0 @@
-assert url_decision("http://user:secret@host:8080", "") == "reject"
@@ -150,1 +149,0 @@
-assert "Do not type the password into this form" in described
@@ -274,1 +272,0 @@
-assert query_url_has_userinfo("http://user:secret@localhost:8093") is True
@@ -318,1 +315,0 @@
-couchbase_query_url="http://user:secret@localhost:8093",

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.7.13. 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: zeus-dev-helper-mcp: Prompting user to enter sensitive 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.9.2) 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/zeus-dev-helper-mcp/0.7.13

## Findings with a location
- `src/zeus_dev_helper_mcp/first_create.py:36` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/first_create.py:36 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/first_create.py:46` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/first_create.py:46 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/first_create.py:40` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/first_create.py:40 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/clarify.py:90` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/clarify.py:90 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/beer.py:1891` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/beer.py:1891 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/llm_key.py:178` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/llm_key.py:178 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/scaffold.py:797` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/scaffold.py:797 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/prompts.py:40` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/prompts.py:40 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/first_create.py:58` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/first_create.py:58 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/beer.py:1248` · URL with embedded credentials — src/zeus_dev_helper_mcp/beer.py:1248 · URL with embedded credentials — may be phishing or credential leaking
- `src/zeus_dev_helper_mcp/llm_key.py:248` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/llm_key.py:248 · Prompting user to enter sensitive credentials — social engineering
- `src/zeus_dev_helper_mcp/first_create.py:53` · Prompting user to enter sensitive credentials — src/zeus_dev_helper_mcp/first_create.py:53 · Prompting user to enter sensitive credentials — social engineering

## Proposed change
The attached patch removes the 20 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 koten-ai/zeus_dev_helper_mcp --clone && cd zeus_dev_helper_mcp
curl -s https://killerskills.ai/skills/pypi/zeus-dev-helper-mcp/0.7.13/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.7.13 && git commit -am "zeus-dev-helper-mcp: Prompting user to enter sensitive credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/zeus-dev-helper-mcp/0.7.13/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.