registry / dsh-tg-bridge / 1.1.2
dsh-tg-bridge@1.1.2
устаревшая сборка — ставьте 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-aiSource inspection found no install hook or confirmed attack behavior. Network use is directed to Telegram, and the inspected global persona write is available through the authorized bridge control command.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Starting the bridge or explicitly running its setup command.
Impact
No confirmed unauthorized credential transfer, data exfiltration, or unconsented control-surface mutation was found.
Mechanism
The bridge uses a locally stored Telegram bot token and checks messages against configured user IDs before handling them. Setup uses local process commands to manage the bridge and scheduled task.
AI rationale
Source inspection found no install hook or confirmed attack behavior. Network use is directed to Telegram, and the inspected global persona write is available through the authorized bridge control command.
Evidence
package.jsonbridge.mjscontrol.mjssetup.mjs
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines runtime entrypoints and user-run scripts, with no install lifecycle hook.
- The control module changes the DSH persona file only through the /soul command.
- The bridge reads its Telegram bot token locally and rejects messages from users outside its configured allowlist.
- setup.mjs is an explicit setup utility; its child-process helper is used by that utility.
- The bridge sends Bot API requests to api.telegram.org.
Evidence against
- Setup invokes local system commands and can update a scheduled task when setup is run.
- The package exposes controls for plugins and for writing the global DSH persona file.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
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.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.1.2 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.