Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/mithwire_mcp/state_store.py b/mithwire_mcp/state_store.py
--- a/mithwire_mcp/state_store.py
+++ b/mithwire_mcp/state_store.py
@@ -440,1 +440,0 @@
-# Proxies (first-class registry of upstream proxy credentials)
@@ -498,1 +497,0 @@
-# Allow ``server`` URL form (``http://user:pass@host:port``) on input;
diff --git a/mithwire_mcp/browser.py b/mithwire_mcp/browser.py
--- a/mithwire_mcp/browser.py
+++ b/mithwire_mcp/browser.py
@@ -321,1 +321,0 @@
-Chromium has no command-line way to pass proxy credentials, so we drive
diff --git a/mithwire_mcp/server.py b/mithwire_mcp/server.py
--- a/mithwire_mcp/server.py
+++ b/mithwire_mcp/server.py
@@ -128,1 +128,0 @@
-"proxy accepts 'http://host:port', 'http://user:pass@host:port', the "
@@ -364,1 +363,0 @@
-"'http://user:pw@host:port', rotation_url, tags}). The persisted "
diff --git a/tests/test_browser.py b/tests/test_browser.py
--- a/tests/test_browser.py
+++ b/tests/test_browser.py
@@ -30,1 +30,0 @@
-proxy = parse_proxy("http://user:[email protected]:8080")
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -134,1 +134,0 @@
-<summary><b>🔁 Session Lifecycle</b></summary> - `session_start` - Launch a new browser session (ephemeral or persistent profile) - `session_list` - List active
@@ -202,1 +201,0 @@
-<summary><b>🔧 Advanced: HTML, JS Evaluation & Tracing</b></summary> - `browser_html` - Get the raw HTML of the current page or an element - `browser_evaluate` 
diff --git a/mithwire_mcp/migrate.py b/mithwire_mcp/migrate.py
--- a/mithwire_mcp/migrate.py
+++ b/mithwire_mcp/migrate.py
@@ -17,1 +17,0 @@
-inlined the same proxy credentials in multiple places. The plan's
diff --git a/tests/test_runtime_proxy_preflight.py b/tests/test_runtime_proxy_preflight.py
--- a/tests/test_runtime_proxy_preflight.py
+++ b/tests/test_runtime_proxy_preflight.py
@@ -184,1 +184,0 @@
-proxy="http://user:[email protected]:8080",
@@ -208,1 +207,0 @@
-proxy="http://user:[email protected]:8080",
@@ -250,1 +248,0 @@
-proxy="http://user:[email protected]:8080",
@@ -283,1 +280,0 @@
-proxy="http://user:[email protected]:8080",
@@ -353,1 +349,0 @@
-proxy="http://user:[email protected]:8080",
diff --git a/tests/test_launch_cleanup.py b/tests/test_launch_cleanup.py
--- a/tests/test_launch_cleanup.py
+++ b/tests/test_launch_cleanup.py
@@ -308,1 +308,0 @@
-headless=True, proxy=parse_proxy("http://user:[email protected]:8080")
diff --git a/tests/test_proxy.py b/tests/test_proxy.py
--- a/tests/test_proxy.py
+++ b/tests/test_proxy.py
@@ -38,1 +38,0 @@
-cfg = parse_proxy("http://user:[email protected]:8080")
@@ -45,1 +44,0 @@
-cfg = parse_proxy("http://us%40er:p%3Aass@host:3128")
@@ -95,1 +93,0 @@
-cfg = parse_proxy("http://user:supersecret@h:8080")
@@ -103,1 +100,0 @@
-cfg = parse_proxy("http://user:supersecret@h:8080")
@@ -152,1 +148,0 @@
-"server": "http://u:[email protected]:8080",
diff --git a/tests/test_proxy_registry.py b/tests/test_proxy_registry.py
--- a/tests/test_proxy_registry.py
+++ b/tests/test_proxy_registry.py
@@ -50,1 +50,0 @@
-"server": "http://user:[email protected]:8081",
diff --git a/tests/test_migrate_command.py b/tests/test_migrate_command.py
--- a/tests/test_migrate_command.py
+++ b/tests/test_migrate_command.py
@@ -19,1 +19,0 @@
-*and* inline the same proxy credentials in two places, so we can verify

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.5.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: mithwire-mcp: Credential pass-through configuration (KillerSkills verdict caution 62)

## 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 62/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/mithwire-mcp/0.5.1

## Findings with a location
- `mithwire_mcp/state_store.py:440` · Credential pass-through configuration — mithwire_mcp/state_store.py:440 · Credential pass-through configuration — agent relays sensitive credentials
- `mithwire_mcp/state_store.py:498` · URL with embedded credentials — mithwire_mcp/state_store.py:498 · URL with embedded credentials — may be phishing or credential leaking
- `mithwire_mcp/browser.py:321` · Credential pass-through configuration — mithwire_mcp/browser.py:321 · Credential pass-through configuration — agent relays sensitive credentials
- `mithwire_mcp/server.py:364` · URL with embedded credentials — mithwire_mcp/server.py:364 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_browser.py:30` · URL with embedded credentials — tests/test_browser.py:30 · URL with embedded credentials — may be phishing or credential leaking
- `mithwire_mcp/server.py:128` · URL with embedded credentials — mithwire_mcp/server.py:128 · URL with embedded credentials — may be phishing or credential leaking
- `README.md:202` · Collapsed <details> block carrying instructions — README.md:202 · Collapsed <details> block carrying instructions
- `mithwire_mcp/migrate.py:17` · Credential pass-through configuration — mithwire_mcp/migrate.py:17 · Credential pass-through configuration — agent relays sensitive credentials
- `README.md:134` · Collapsed <details> block carrying instructions — README.md:134 · Collapsed <details> block carrying instructions
- `tests/test_runtime_proxy_preflight.py:208` · URL with embedded credentials — tests/test_runtime_proxy_preflight.py:208 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_launch_cleanup.py:308` · URL with embedded credentials — tests/test_launch_cleanup.py:308 · URL with embedded credentials — may be phishing or credential leaking
- `tests/test_proxy.py:103` · URL with embedded credentials — tests/test_proxy.py:103 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 22 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._