registry / dsh-tg-bridge / 1.33.1
dsh-tg-bridge@1.33.1
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s command execution and network activity serve its stated Telegram bridge and setup functions. No install hook or unrelated credential destination was found.
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 user runs setup or starts the bridge; the plugin can start it after configuration exists.
Impact
These network actions support the package’s stated bridge and diagnostics functions; no unrelated collection or harmful action was identified.
Mechanism
Setup validates the Telegram token with Telegram. The model probe uses the configured provider URL and key for a brief ping.
AI rationale
The package’s command execution and network activity serve its stated Telegram bridge and setup functions. No install hook or unrelated credential destination was found.
Evidence
~/.dsh/tg-bridge/config.json~/.dsh/tg-bridge/bridge.log~/.dsh/tg-bridge/setup.log~/.dsh/.credentials.yaml
Network endpoints2
api.telegram.org/bot<botToken>/getMe<profile-configured provider baseUrl>/chat/completions
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines explicit start, setup, check, and hook commands, with no install lifecycle script.
- The plugin starts the bridge only after a config file exists and no bridge is already running.
- The model probe uses a provider URL from the user’s profile and sends that provider’s key with a one-token ping.
- Setup checks the configured Telegram bot token against Telegram’s own getMe endpoint.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
10 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 Medium5 Low
CriticalCommand Output Exfiltrationsetup.mjs#virtual:normalized:round1
CriticalPrevious Version Dangerous Deltabridge.mjs
HighChild Processinstall-hooks.mjs
HighShellsetup.mjs#virtual:normalized:round1
HighSame File Env Network Executionsetup.mjs#virtual:normalized:round1
HighSemantic Analysis Limitedcontrol/release.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.33.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.33.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.