registry / dsh-tg-bridge / 1.43.0
dsh-tg-bridge@1.43.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged command execution and network activity serve explicit setup, bridge supervision, or configured provider features. No install hook or flow sending credentials or command output to an unrelated host was found.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The bridge starts after configuration during host startup; setup, model probing, and transcription run through their corresponding user actions or requested features.
Impact
Expected operation of the bridge and requested provider features; no unrelated collection or attack behavior was identified.
Mechanism
The package sends the Telegram bot token to Telegram and sends configured provider keys with model probes or audio transcription requests to the configured service endpoints.
AI rationale
The flagged command execution and network activity serve explicit setup, bridge supervision, or configured provider features. No install hook or flow sending credentials or command output to an unrelated host was found.
Network endpoints3
api.telegram.orgprovider.baseUrl (configured)voice.baseUrl (configured)
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest lists explicit start, setup, check, menu, and doctor scripts; it declares no install lifecycle hook.
- The plugin starts the bridge only when a config file exists and no bridge is already running.
- Model probes send the selected model and its key to the provider base URL configured in the DSH profile.
- Voice transcription sends the selected audio and configured key to the configured speech endpoint.
- Setup is an explicit CLI action; its token check calls Telegram's api.telegram.org getMe endpoint.
Evidence against
- The installer registers autostart by default when a user runs install.sh, but this starts the package's Telegram bridge.
- The package reads configured service credentials and handles message attachments, so expected service traffic includes user-authorized data.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
9 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
1 Critical6 High4 Medium5 Low
CriticalCommand Output Exfiltrationsetup.mjs#virtual:normalized:round1
HighChild Processinstall-hooks.mjs
HighShellsetup.mjs#virtual:normalized:round1
HighSame File Env Network Executionsetup.mjs#virtual:normalized:round1
HighSemantic Analysis Limitedchat/media.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritywork/bridge-restart-idle.mjs
HighKnown Malware Source Similaritywork/restart-after-send.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperinstall.sh
MediumStructural Risk Force Deep Review
LowScripts Present
Low
Affected versions and remediation
This report applies to dsh-tg-bridge@1.43.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.43.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.