Propose a patch

Evidence

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

diff --git a/src/netexec_mcp/modules/ldap.py b/src/netexec_mcp/modules/ldap.py
--- a/src/netexec_mcp/modules/ldap.py
+++ b/src/netexec_mcp/modules/ldap.py
@@ -181,1 +181,0 @@
-Reports OS/domain and the auth result (`[+]`/`[-]`). Pass credentials to bind,
diff --git a/src/netexec_mcp/modules/rdp.py b/src/netexec_mcp/modules/rdp.py
--- a/src/netexec_mcp/modules/rdp.py
+++ b/src/netexec_mcp/modules/rdp.py
@@ -122,1 +122,0 @@
-the auth result (`[+]`, with `Pwn3d!` when the account can log in). Pass credentials
diff --git a/src/netexec_mcp/modules/mssql.py b/src/netexec_mcp/modules/mssql.py
--- a/src/netexec_mcp/modules/mssql.py
+++ b/src/netexec_mcp/modules/mssql.py
@@ -146,1 +146,0 @@
-role). Pass credentials to authenticate, or none to fingerprint the service.
diff --git a/src/netexec_mcp/modules/winrm.py b/src/netexec_mcp/modules/winrm.py
--- a/src/netexec_mcp/modules/winrm.py
+++ b/src/netexec_mcp/modules/winrm.py
@@ -104,1 +104,0 @@
-open a remote shell). Pass credentials to authenticate, or none to probe whether
diff --git a/src/netexec_mcp/modules/wmi.py b/src/netexec_mcp/modules/wmi.py
--- a/src/netexec_mcp/modules/wmi.py
+++ b/src/netexec_mcp/modules/wmi.py
@@ -116,1 +116,0 @@
-account is a local admin). Pass credentials to authenticate, or none to fingerprint

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.10. 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: netexec-mcp: Credential pass-through configuration (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/netexec-mcp/1.0.10

## Findings with a location
- `src/netexec_mcp/modules/ldap.py:181` · Credential pass-through configuration — src/netexec_mcp/modules/ldap.py:181 · Credential pass-through configuration — agent relays sensitive credentials
- `src/netexec_mcp/modules/rdp.py:122` · Credential pass-through configuration — src/netexec_mcp/modules/rdp.py:122 · Credential pass-through configuration — agent relays sensitive credentials
- `src/netexec_mcp/modules/mssql.py:146` · Credential pass-through configuration — src/netexec_mcp/modules/mssql.py:146 · Credential pass-through configuration — agent relays sensitive credentials
- `src/netexec_mcp/modules/winrm.py:104` · Credential pass-through configuration — src/netexec_mcp/modules/winrm.py:104 · Credential pass-through configuration — agent relays sensitive credentials
- `src/netexec_mcp/modules/wmi.py:116` · Credential pass-through configuration — src/netexec_mcp/modules/wmi.py:116 · Credential pass-through configuration — agent relays sensitive credentials

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