registry / dsh-tg-bridge / 1.7.5
dsh-tg-bridge@1.7.5
устаревшая сборка — ставьте 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 10d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook. Source inspection shows configured Telegram traffic, allowlisted command handling, and explicit or maintenance-scoped process actions; no concrete attack surface was found.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The bridge runs when started or enabled in its host; message handling requires an allowed Telegram user or chat. Setup and app restart actions require explicit commands.
Impact
No unrelated credential transfer, unauthorized account action, or unconsented agent configuration change was established.
Mechanism
The bridge forwards turns and replies through the Telegram Bot API, passes configured provider keys to the local DeepSeek Harness process, and uses a public catalog for optional price lookups.
AI rationale
The manifest has no install lifecycle hook. Source inspection shows configured Telegram traffic, allowlisted command handling, and explicit or maintenance-scoped process actions; no concrete attack surface was found.
Network endpoints2
api.telegram.orgmodels.dev
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes runtime start and setup commands but no install lifecycle hook.
- The bridge reads its Telegram token from configured local sources, sends through the Telegram Bot API, and ignores messages from users or chats outside its configured allowlist.
- Provider keys are selected from the configured providerKeys list and passed to the local DeepSeek Harness process for a turn.
- The persona file is changed only by the explicit /soul command, which is reached after the bridge checks the sender against its allowlist.
- The optional model-price lookup uses the public models.dev catalog.
- Process-management code is for bridge or DeepSeek Harness maintenance; app restart requires an explicit confirmation, and the helper files wait for idle time or delivery.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
8 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 · L19control.mjsView file
1129try {
L1130: const drives = execFileSync('powershell', ['-NoProfile', '-NonInteractive', '-Command', '(Get-PSDrive C).Free'], {
L1131: encoding: 'utf8',
Findings
1 Critical6 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
HighChild Processsetup.mjs
HighShellcontrol.mjs
HighCommand Output Exfiltrationsetup.mjs
HighSemantic Analysis Limitedprices.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritybridge-restart-idle.mjs
HighKnown Malware Source Similarityrestart-after-send.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpertranscribe.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.7.5.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.7.5 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.