registry / dsh-tg-bridge / 1.11.0
dsh-tg-bridge@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-aiDirect source inspection did not support the scanner’s exfiltration label: the bridge uses Telegram’s API, while configured provider keys are passed to a local DSH child process. The persistent persona write is invoked through /soul by an allowlisted user, and the package has no install lifecycle hook.
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
A configured user starts the bridge or sends it an authorized Telegram command.
Impact
No malicious transfer, unauthorized agent configuration change, or install-time action was established.
Mechanism
The bridge polls Telegram, forwards authorized requests to a local DSH process, and uses Telegram’s API for replies. Provider keys are copied to that local process only when explicitly listed in configuration.
AI rationale
Direct source inspection did not support the scanner’s exfiltration label: the bridge uses Telegram’s API, while configured provider keys are passed to a local DSH child process. The persistent persona write is invoked through /soul by an allowlisted user, and the package has no install lifecycle hook.
Evidence
package.jsonbridge.mjscontrol.mjsprices.mjsprofile-edit.mjssetup.mjsbridge-restart-idle.mjsrestart-after-send.mjs
Network endpoints2
api.telegram.orgmodels.dev/api.json
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 lists normal command scripts and no preinstall, install, or postinstall hook.
- bridge.mjs uses the configured bot token with Telegram’s API and ignores messages from senders outside the configured allowed user or chat IDs.
- Provider keys are passed to the local DSH child process only when named in providerKeys; the example configuration leaves that list empty.
- The /soul command writes the supplied text to the AGENTS persona section, and bridge.mjs gates incoming messages on the configured allowlist.
- The flagged control operations correspond to local profile, permission, plugin, application, language, and session controls.
- The price lookup uses the public models.dev catalog, while the restart helpers relaunch the local bridge.
Evidence against
- The scanner’s exfiltration label is not supported by the inspected transfer paths: the bridge sends Telegram API requests, and provider keys go to the local DSH process.
- The agent configuration write requires an allowed user to invoke /soul; it is not an automatic install-time mutation.
Behavioral surface
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 Helpertranscribe.py
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to dsh-tg-bridge@1.11.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.11.0 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.