Propose a patch

Evidence

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

diff --git a/dist/setup.js b/dist/setup.js
--- a/dist/setup.js
+++ b/dist/setup.js
@@ -263,1 +263,0 @@
-print('  enter the credentials below. Leave blank if no server password is needed.', c.dim);
diff --git a/dist/config.js b/dist/config.js
--- a/dist/config.js
+++ b/dist/config.js
@@ -443,1 +443,0 @@
-// v6.11.11: Strip a UTF-8 BOM ("") off the start of a config payload
@@ -445,1 +444,0 @@
-// silently writes a BOM, and JSON.parse rejects with "Unexpected token "
diff --git a/dist/chat-hygiene.js b/dist/chat-hygiene.js
--- a/dist/chat-hygiene.js
+++ b/dist/chat-hygiene.js
@@ -23,1 +23,0 @@
-const JUNK_CHARS = /[\u0000-\u0008\u000B\u000C\u000E-\u001F\u007F-\u009F]/g;
@@ -216,1 +215,0 @@
-const text = raw.replace(/^/, '');
@@ -254,1 +252,0 @@
-const text = raw.replace(/^/, '');
diff --git a/dist/code-policy.js b/dist/code-policy.js
--- a/dist/code-policy.js
+++ b/dist/code-policy.js
@@ -73,1 +73,0 @@
-let s = src.replace(/^/, '');
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -1190,1 +1190,0 @@
-<summary><b>Connection failed</b></summary> 1. Check API key: WordPress > Respira > API Keys 2. URL must include `https://` 3. Plugin must be activated 4. Check
@@ -1228,1 +1227,0 @@
-<summary><b>Tools not showing</b></summary> 1. Restart your AI tool completely 2. Validate JSON syntax in config file 3. Check config file location 4. Run `npx 
diff --git a/dist/skill-prompts.js b/dist/skill-prompts.js
--- a/dist/skill-prompts.js
+++ b/dist/skill-prompts.js
@@ -35,1 +35,0 @@
-let body = markdown.replace(/^/, '');

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 8.7.7. 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: wordpress-mcp-server: Prompting user to enter sensitive credentials (KillerSkills verdict caution 57)

## 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 57/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/wordpress-mcp-server/8.7.7

## Findings with a location
- `dist/setup.js:263` · Prompting user to enter sensitive credentials — dist/setup.js:263 · Prompting user to enter sensitive credentials — social engineering
- `dist/config.js:443` · Hidden zero-width characters detected — dist/config.js:443 · Hidden zero-width characters detected — may conceal content
- `dist/chat-hygiene.js:23` · Hidden zero-width characters detected — dist/chat-hygiene.js:23 · Hidden zero-width characters detected — may conceal content
- `dist/code-policy.js:73` · Hidden zero-width characters detected — dist/code-policy.js:73 · Hidden zero-width characters detected — may conceal content
- `dist/chat-hygiene.js:216` · Hidden zero-width characters detected — dist/chat-hygiene.js:216 · Hidden zero-width characters detected — may conceal content
- `README.md:1228` · Collapsed <details> block carrying instructions — README.md:1228 · Collapsed <details> block carrying instructions
- `README.md:1190` · Collapsed <details> block carrying instructions — README.md:1190 · Collapsed <details> block carrying instructions
- `dist/skill-prompts.js:35` · Hidden zero-width characters detected — dist/skill-prompts.js:35 · Hidden zero-width characters detected — may conceal content
- `dist/config.js:445` · Hidden zero-width characters detected — dist/config.js:445 · Hidden zero-width characters detected — may conceal content
- `dist/chat-hygiene.js:254` · Hidden zero-width characters detected — dist/chat-hygiene.js:254 · Hidden zero-width characters detected — may conceal content

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