registry / dsh-tg-bridge / 1.1.1
dsh-tg-bridge@1.1.1
устаревшая сборка — ставьте 1.11.0 или новее
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected network requests use Telegram's API for bridge operation and setup checks. The scanner's exfiltration and command-execution indicators correspond to expected bridge and DSH control behavior, with inbound messages restricted by an allowlist.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The bridge starts when explicitly run; setup and control operations require their respective commands or allowlisted Telegram messages.
Impact
The inspected behavior supports the described bridge functions; no confirmed unauthorized disclosure or mutation was found.
Mechanism
The bridge uses its configured Telegram bot token with Telegram's API, filters incoming users by an allowlist, and passes requested work to the local DSH application.
AI rationale
The manifest has no install hook, and inspected network requests use Telegram's API for bridge operation and setup checks. The scanner's exfiltration and command-execution indicators correspond to expected bridge and DSH control behavior, with inbound messages restricted by an allowlist.
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle hook; its scripts expose the bridge and setup through explicit commands.
- The bridge reads its Telegram bot token and constructs requests to Telegram's API.
- The bridge ignores messages from users and chats outside its configured allowlist.
- The persona update is an explicit control command that writes the DSH persona section; the surrounding function preserves the rest of the instructions file.
- The inspected bridge operations handle local transcription, DSH process output, and named DSH process control; no unrelated receiver or destructive target was found.
- Setup checks the Telegram token with Telegram's getMe endpoint.
Evidence against
- Scanner labels suggested data exfiltration and command-output exfiltration, but inspected source did not show credentials or application records sent to an unrelated recipient.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flaggedsetup.mjsView file
19L20: import { spawnSync } from 'node:child_process';
L21: import { appendFileSync, existsSync, readFileSync, openSync, closeSync, unlinkSync, writeFileSync } from 'node:fs';
High
19L20: import { spawnSync } from 'node:child_process';
L21: import { appendFileSync, existsSync, readFileSync, openSync, closeSync, unlinkSync, writeFileSync } from 'node:fs';
...
L24:
L25: const DSH_HOME = process.env.DSH_HOME || join(homedir(), '.dsh');
L26: const BRIDGE_DIR = join(DSH_HOME, 'tg-bridge');
...
L48: let held = 0;
L49: try { held = Number(JSON.parse(readFileSync(LOCK, 'utf8')).pid) || 0; } catch {}
L50: let alive = false;
...
L63: /**
L64: * Every step is written to setup.log as well as stdout.
L65: *
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
setup.mjsView on unpkg · L19bridge.mjsView file
7Source sends the broad process environment to a literal external destination.
L7: // the logon task (see README.md).
L8: import { spawn } from 'node:child_process';
L9: import {
...
L18: // 5.3 s, IPv6 to GitHub 0.02 s refused). The --dns-result-order flag alone
L19: // does not bind fetch/undici, so pin the family on the socket layer.
L20: import dns from 'node:dns';
L21: import net from 'node:net';
...
L27:
L28: const HOME = homedir();
L29: const DIR = join(HOME, '.dsh', 'tg-bridge');
...
L38: // bridge mirrors that exactly so no shell quoting of task text is needed.
L39: const APP = join(process.env.LOCALAPPDATA || '', 'Programs', 'DeepSeek Harness');
Findings
1 Critical2 High4 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
HighChild Processsetup.mjs
HighCommand Output Exfiltrationsetup.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpertranscribe.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to dsh-tg-bridge@1.1.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.1.1 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.