registry / dsh-tg-bridge / 1.22.0
dsh-tg-bridge@1.22.0
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged command execution is used for bridge supervision, diagnostics and user-invoked Git hook setup. Network calls target Telegram’s API for bot checks and handling media, and the plugin starts only when a configured runtime is present.
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
Bridge startup requires a configured runtime; setup, diagnostics and hook installation are command-driven.
Impact
No malicious impact identified in the reviewed source.
Mechanism
The plugin launches the bridge when configured, and the bridge uses Telegram’s API for bot checks and user-submitted media.
AI rationale
The flagged command execution is used for bridge supervision, diagnostics and user-invoked Git hook setup. Network calls target Telegram’s API for bot checks and handling media, and the plugin starts only when a configured runtime is present.
Evidence
~/.dsh/tg-bridge/bridge.pid~/.dsh/tg-bridge/plugin-start.lock~/.dsh/tg-bridge/setup.log~/.dsh/tg-bridge/inbox/
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package declares no runtime dependencies.
- The plugin starts the bridge only when autoStart is enabled and a configuration file exists.
- Setup probes Telegram’s official getMe endpoint using the configured bot token.
- Media downloads are fetched from Telegram’s official file API as part of handling user-sent media.
Evidence against
- The package includes commands that restart the bridge and install Git secret-scanning hooks; these are explicit setup or user-invoked actions.
- The inspected source showed no unrelated collector or automatic command-output exfiltration.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggedinstall-hooks.mjsView file
13// Usage: node install-hooks.mjs [--uninstall]
L14: import { execFileSync } from 'node:child_process';
L15: import { existsSync, mkdirSync, chmodSync, writeFileSync } from 'node:fs';
High
setup.mjs#virtual:normalized:round1View file
107try {
L108: const r = run("powershell", [
L109: "-NoProfile", "-NonInteractive", "-Command",
...
L111: ]);
L112: return Number((r.stdout || "").trim()) || 0;
L113: } catch {
...
L117:
L118: /** True when the pid exists — EPERM still means alive (another user"s process). */\r\nfunction alive(pid) {\r\n try {\r\n process.kill(pid, 0);\r\n return true;\r\n } catc...
L119: // bridge" and both start a poller (409 getUpdates Conflict). Going through\r\n // bridge-kick.mjs means every start happens under restart.lock after a check.\r\n c...
Critical
Command Output Exfiltration
Source executes local commands and sends command output to an external endpoint.
setup.mjs#virtual:normalized:round1View on unpkg · L107Findings
2 Critical6 High4 Medium4 Low
CriticalCommand Output Exfiltrationsetup.mjs#virtual:normalized:round1
CriticalPrevious Version Dangerous Deltacontrol/cmd-bridge.mjs
HighChild Processinstall-hooks.mjs
HighShellsetup.mjs#virtual:normalized:round1
HighSame File Env Network Executionsetup.mjs#virtual:normalized:round1
HighSemantic Analysis Limitedmedia.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
Affected versions and remediation
This report applies to dsh-tg-bridge@1.22.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.22.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.