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. 69 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/tests/test_session_string_generator.py b/tests/test_session_string_generator.py
--- a/tests/test_session_string_generator.py
+++ b/tests/test_session_string_generator.py
@@ -105,1 +105,0 @@
-assert prompted == ["\nTwo-factor authentication enabled. Please enter your password: "]
@@ -136,1 +135,0 @@
-assert prompted == ["Two-factor authentication enabled. Please enter your password: "]
diff --git a/session_string_generator.py b/session_string_generator.py
--- a/session_string_generator.py
+++ b/session_string_generator.py
@@ -148,1 +148,0 @@
-"\nTwo-factor authentication enabled. Please enter your password: "
@@ -180,1 +179,0 @@
-pw = getpass.getpass("Two-factor authentication enabled. Please enter your password: ")
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.0.5. 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: uniquedivine-telegram-mcp: Prompting user to enter sensitive credentials (KillerSkills verdict caution 69)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 69/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/uniquedivine-telegram-mcp/2.0.5 ## Findings with a location - `tests/test_session_string_generator.py:136` · Prompting user to enter sensitive credentials — tests/test_session_string_generator.py:136 · Prompting user to enter sensitive credentials — social engineering - `session_string_generator.py:148` · Prompting user to enter sensitive credentials — session_string_generator.py:148 · Prompting user to enter sensitive credentials — social engineering - `tests/test_session_string_generator.py:105` · Prompting user to enter sensitive credentials — tests/test_session_string_generator.py:105 · Prompting user to enter sensitive credentials — social engineering - `session_string_generator.py:180` · Prompting user to enter sensitive credentials — session_string_generator.py:180 · Prompting user to enter sensitive credentials — social engineering ## Proposed change The attached patch removes the 4 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 Unique-Divine/jiyuu --clone && cd jiyuu curl -s https://killerskills.ai/skills/pypi/uniquedivine-telegram-mcp/2.0.5/patch.diff | git apply --unidiff-zero git checkout -b killerskills/2.0.5 && git commit -am "uniquedivine-telegram-mcp: Prompting user to enter sensitive credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/uniquedivine-telegram-mcp/2.0.5/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.