Propose a patch

Evidence

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

diff --git a/server.py b/server.py
--- a/server.py
+++ b/server.py
@@ -849,1 +849,0 @@
-output.append(f"echo {encoded} | base64 -d | bash")
diff --git a/src/nobody_pentest_mcp/server.py b/src/nobody_pentest_mcp/server.py
--- a/src/nobody_pentest_mcp/server.py
+++ b/src/nobody_pentest_mcp/server.py
@@ -849,1 +849,0 @@
-output.append(f"echo {encoded} | base64 -d | bash")

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.0.6. 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: nobody-pentest-mcp: Host or command assembled from base64 fragments (KillerSkills verdict caution 68)

## 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 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/nobody-pentest-mcp/2.0.6

## Findings with a location
- `server.py:849` · Host or command assembled from base64 fragments — server.py:849 · Host or command assembled from base64 fragments
- `src/nobody_pentest_mcp/server.py:849` · Host or command assembled from base64 fragments — src/nobody_pentest_mcp/server.py:849 · Host or command assembled from base64 fragments

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