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. 60 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 3 caught lines
Download .patchdiff --git a/src/mcp_audit/injection.py b/src/mcp_audit/injection.py --- a/src/mcp_audit/injection.py +++ b/src/mcp_audit/injection.py @@ -66,1 +66,0 @@ -"pass token", diff --git a/src/mcp_audit/integrity.py b/src/mcp_audit/integrity.py --- a/src/mcp_audit/integrity.py +++ b/src/mcp_audit/integrity.py @@ -86,1 +86,0 @@ -(e.g. ``--token-file ~/.aws/credentials``), but even their SHA-256 should not diff --git a/src/mcp_audit/rules/result_injection.py b/src/mcp_audit/rules/result_injection.py --- a/src/mcp_audit/rules/result_injection.py +++ b/src/mcp_audit/rules/result_injection.py @@ -34,1 +34,0 @@ -# Concrete secret locations and names. "~/.ssh/config" is host-alias
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.0.0. 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: mcp-audits: Credential pass-through configuration (KillerSkills verdict caution 60)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 60/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/mcp-audits/3.0.0 ## Findings with a location - `src/mcp_audit/injection.py:66` · Credential pass-through configuration — src/mcp_audit/injection.py:66 · Credential pass-through configuration — agent relays sensitive credentials - `src/mcp_audit/integrity.py:86` · References a credential file in the home directory — src/mcp_audit/integrity.py:86 · References a credential file in the home directory - `src/mcp_audit/rules/result_injection.py:34` · Reads credential paths from the home directory — src/mcp_audit/rules/result_injection.py:34 · Reads credential paths from the home directory ## Proposed change The attached patch removes the 3 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 saagpatel/MCPAudit --clone && cd MCPAudit curl -s https://killerskills.ai/skills/pypi/mcp-audits/3.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/3.0.0 && git commit -am "mcp-audits: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/mcp-audits/3.0.0/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.