registry / dsh-tg-bridge / 1.7.4
dsh-tg-bridge@1.7.4
устаревшая сборка — ставьте 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-aiSource inspection found no install hook or confirmed attack behavior. The flagged network, configuration, and process operations align with the Telegram bridge, model-price lookup, and user-invoked controls.
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 when DSH loads the plugin with a runtime configuration; other changes follow setup or chat commands.
Impact
No confirmed malicious effect or unrelated data disclosure was established.
Mechanism
The inspected code sends bridge requests to Telegram, retrieves public model-price data, and manages bridge state and processes.
AI rationale
Source inspection found no install hook or confirmed attack behavior. The flagged network, configuration, and process operations align with the Telegram bridge, model-price lookup, and user-invoked controls.
Network endpoints2
api.telegram.orgmodels.dev
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies a Telegram bridge and has no install lifecycle hook.
- The DSH persona file is changed through the explicit /soul command.
- bridge.mjs sends bridge messages to Telegram’s API; prices.mjs fetches a model catalog to render prices.
- setup.mjs and the restart helpers manage the bridge process and wait for idle or reply delivery.
- The /plugin operations are invoked through a chat command.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 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
•matchType = previous_version_dangerous_delta
matchedPackage = dsh-tg-bridge@1.7.2
matchedIdentity = npm:ZHNoLXRnLWJyaWRnZQ:1.7.2
similarity = 0.920
summary = stored previous version shares package body but lacks this dangerous source file
Findings
2 Critical6 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
CriticalPrevious Version Dangerous Deltacontrol.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
Affected versions and remediation
This report applies to dsh-tg-bridge@1.7.4.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.7.4 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.