registry / dsh-tg-bridge / 1.19.11
dsh-tg-bridge@1.19.11
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection supports configured-provider authentication and Telegram bridge behavior. The manifest has no install lifecycle hook, and the inspected persona write is explicit-command driven; no concrete attack behavior was identified.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The bridge starts through its plugin or CLI; a provider probe runs during fallback handling when a model fails.
Impact
No unrelated credential disclosure or unconsented agent configuration change was established.
Mechanism
The probe reads the configured provider URL and key, then sends a minimal request to that provider. The persona file write requires the explicit `/soul` command with supplied text.
AI rationale
Source inspection supports configured-provider authentication and Telegram bridge behavior. The manifest has no install lifecycle hook, and the inspected persona write is explicit-command driven; no concrete attack behavior was identified.
Evidence
package.jsonplugin-bridge.mjsbridge.mjsmodel-probe.mjscontrol.mjspanel.mjssettings-card.mjsprofile-edit.mjssetup.mjsinstall-hooks.mjsbridge-restart-idle.mjsrestart-after-send.mjs
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines the bridge entry points and ordinary commands, with no install lifecycle hook.
- During fallback handling, the bridge probes the first configured provider using its configured URL and key name, sending a one-token ping.
- The bridge and setup check communicate with Telegram’s API for bot operations and health checks.
- The persona file is written only when the explicit `/soul` command receives text; the other inspected runtime locations cover bridge processing, settings, status display and process management.
- The inspected profile editor, setup, hook and restart helpers support configuration, health checks, explicit secret scanning or bridge process management.
Evidence against
- No inspected source established an unrelated credential recipient, covert collection or an unconsented agent configuration change.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
11 flaggedinstall-hooks.mjsView file
13// Usage: node install-hooks.mjs [--uninstall]
L14: import { execFileSync } from 'node:child_process';
L15: import { existsSync, mkdirSync, chmodSync, writeFileSync } from 'node:fs';
High
setup.mjs#virtual:normalized:round1View file
107try {
L108: const r = run("powershell", [
L109: "-NoProfile", "-NonInteractive", "-Command",
...
L111: ]);
L112: return Number((r.stdout || "").trim()) || 0;
L113: } catch {
...
L117:
L118: /** True when the pid exists — EPERM still means alive (another user"s process). */\r\nfunction alive(pid) {\r\n try {\r\n process.kill(pid, 0);\r\n return true;\r\n } catc...
L119: // bridge" and both start a poller (409 getUpdates Conflict). Going through\r\n // bridge-kick.mjs means every start happens under restart.lock after a check.\r\n c...
Critical
Command Output Exfiltration
Source executes local commands and sends command output to an external endpoint.
setup.mjs#virtual:normalized:round1View on unpkg · L107Findings
3 Critical7 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
CriticalCommand Output Exfiltrationsetup.mjs#virtual:normalized:round1
CriticalPrevious Version Dangerous Deltabridge.mjs
HighChild Processinstall-hooks.mjs
HighShellsetup.mjs#virtual:normalized:round1
HighSame File Env Network Executionsetup.mjs#virtual:normalized:round1
HighTrigger Reachable External Ai Agent Control Surface Mutationcontrol.mjs
HighSemantic Analysis Limitedpanel.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritybridge-restart-idle.mjs
HighKnown Malware Source Similarityrestart-after-send.mjs
MediumNetwork
Affected versions and remediation
This report applies to dsh-tg-bridge@1.19.11.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.11 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.