dsh-tg-bridge@1.19.0
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the reviewed credential transfer is authentication to the provider selected by the active profile. The agent instruction file change is invoked through the bridge's explicit /soul command; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json has no install lifecycle hook; setup, checks, and hook installation are named user-run commands.
- The model probe gets the active profile’s provider URL and key name, then sends the key in authorization for a one-token ping to that provider.
- Telegram bridge requests use the Telegram API host.
- The AGENTS.md persona write is reached through the /soul command when it receives text; the file is under the DSH home directory.
- The inspected control, panel, settings, and profile code handles bridge settings, status, and user-requested operations; no attack behavior was identified.
- The /soul command can change AGENTS.md, which affects agent instructions, but the write is tied to that explicit command.
- The model probe sends a saved or environment-provided provider key to the configured provider URL as authentication.
Source & flagged code
10 flaggedFindings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.19.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.