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. 77 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 3 caught lines
Download .patchdiff --git a/oracle/data_studio_mcp_server/tests/test_unit.py b/oracle/data_studio_mcp_server/tests/test_unit.py
--- a/oracle/data_studio_mcp_server/tests/test_unit.py
+++ b/oracle/data_studio_mcp_server/tests/test_unit.py
@@ -431,1 +431,0 @@
-'''Passwords in URL userinfo (https://user:pass@host).'''
@@ -433,1 +432,0 @@
-msg = ('Connection to https://weblogic:welcome1@'
diff --git a/oracle/data_studio_mcp_server/tools/_helpers.py b/oracle/data_studio_mcp_server/tools/_helpers.py
--- a/oracle/data_studio_mcp_server/tools/_helpers.py
+++ b/oracle/data_studio_mcp_server/tools/_helpers.py
@@ -32,1 +32,0 @@
-# URL with userinfo: https://user:password@host
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.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: oracle.data-studio-mcp-server: URL with embedded credentials (KillerSkills verdict caution 77)
## 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 77/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/oracle.data-studio-mcp-server/2.0.0 ## Findings with a location - `oracle/data_studio_mcp_server/tests/test_unit.py:431` · URL with embedded credentials — oracle/data_studio_mcp_server/tests/test_unit.py:431 · URL with embedded credentials — may be phishing or credential leaking - `oracle/data_studio_mcp_server/tools/_helpers.py:32` · URL with embedded credentials — oracle/data_studio_mcp_server/tools/_helpers.py:32 · URL with embedded credentials — may be phishing or credential leaking - `oracle/data_studio_mcp_server/tests/test_unit.py:433` · URL with embedded credentials — oracle/data_studio_mcp_server/tests/test_unit.py:433 · URL with embedded credentials — may be phishing or credential leaking ## 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 oracle/mcp --clone && cd mcp curl -s https://killerskills.ai/skills/pypi/oracle.data-studio-mcp-server/2.0.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/2.0.0 && git commit -am "oracle.data-studio-mcp-server: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/oracle.data-studio-mcp-server/2.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.