registry / dsh-tg-bridge / 1.12.1
dsh-tg-bridge@1.12.1
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 lifecycle hook or concrete attack behavior. The reported network and process operations fit the Telegram bridge and harness management functions; the scanner labels alone do not establish exfiltration or malware.
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 through its plugin or CLI entrypoint after configuration; no automatic install trigger is declared.
Impact
No malicious impact was established from the inspected source.
Mechanism
The inspected code handles Telegram messages, harness output, status panels, and explicit control commands.
AI rationale
Source inspection found no lifecycle hook or concrete attack behavior. The reported network and process operations fit the Telegram bridge and harness management functions; the scanner labels alone do not establish exfiltration or malware.
Network endpoints2
api.telegram.orgmodels.dev
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest declares no lifecycle hooks and identifies the bridge plugin and CLI as entrypoints.
- The control module’s agent-file write occurs in an explicit command handler; its runtime operations cover user-facing control commands.
- The bridge runtime excerpts process audio and harness output; the panel excerpts format and bound status text.
- The setup and restart helpers describe bridge maintenance; the inspected files show no attack behavior.
- The bridge uses Telegram’s API for its stated messaging function; the inspected source does not establish unrelated credential exfiltration.
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
1620try {
L1621: const drives = execFileSync('powershell', ['-NoProfile', '-NonInteractive', '-Command', '(Get-PSDrive C).Free'], {
L1622: encoding: 'utf8',
Findings
2 Critical6 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
CriticalPrevious Version Dangerous Deltabridge.mjs
HighChild Processsetup.mjs
HighShellcontrol.mjs
HighCommand Output Exfiltrationsetup.mjs
HighSemantic Analysis Limitedpanel.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritybridge-restart-idle.mjs
HighKnown Malware Source Similarityrestart-after-send.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperinstall.sh
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to dsh-tg-bridge@1.12.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.12.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.