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. 68 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/telegram_ai_cli_mcp/outbox.py b/telegram_ai_cli_mcp/outbox.py --- a/telegram_ai_cli_mcp/outbox.py +++ b/telegram_ai_cli_mcp/outbox.py @@ -7,1 +7,0 @@ -delivery mechanism attached — ``~/.ssh/id_ed25519``, the ``.session`` file that diff --git a/telegram_ai_cli_mcp/config.py b/telegram_ai_cli_mcp/config.py --- a/telegram_ai_cli_mcp/config.py +++ b/telegram_ai_cli_mcp/config.py @@ -277,1 +277,0 @@ -"""Encryption at rest for api_hash and proxy credentials. diff --git a/tests/test_render.py b/tests/test_render.py --- a/tests/test_render.py +++ b/tests/test_render.py @@ -60,1 +60,0 @@ [email protected]("invisible", ["", "", "", "", ""]) diff --git a/telegram_ai_cli_mcp/render.py b/telegram_ai_cli_mcp/render.py --- a/telegram_ai_cli_mcp/render.py +++ b/telegram_ai_cli_mcp/render.py @@ -39,1 +39,0 @@ -_INVISIBLE = frozenset("")
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.3. 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: telegram-ai-cli-mcp: References a credential file in the home directory (KillerSkills verdict caution 68)
## 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 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/telegram-ai-cli-mcp/0.1.3 ## Findings with a location - `telegram_ai_cli_mcp/outbox.py:7` · References a credential file in the home directory — telegram_ai_cli_mcp/outbox.py:7 · References a credential file in the home directory - `telegram_ai_cli_mcp/config.py:277` · Credential pass-through configuration — telegram_ai_cli_mcp/config.py:277 · Credential pass-through configuration — agent relays sensitive credentials - `tests/test_render.py:60` · Hidden zero-width characters detected — tests/test_render.py:60 · Hidden zero-width characters detected — may conceal content - `telegram_ai_cli_mcp/render.py:39` · Hidden zero-width characters detected — telegram_ai_cli_mcp/render.py:39 · Hidden zero-width characters detected — may conceal content ## 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 stufently/telegram-ai-cli-mcp --clone && cd telegram-ai-cli-mcp curl -s https://killerskills.ai/skills/pypi/telegram-ai-cli-mcp/0.1.3/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.3 && git commit -am "telegram-ai-cli-mcp: References a credential file in the home directory" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/telegram-ai-cli-mcp/0.1.3/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.