registry / dsh-tg-bridge / 1.34.0
dsh-tg-bridge@1.34.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged command execution is part of an explicitly invoked setup utility, and its token check targets Telegram. Model probes send the configured provider key and a minimal ping to the configured provider endpoint; no unrelated credential destination or automatic install-time behavior was found.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Setup runs through an explicit npm command; model probes run as part of bridge behavior; plugin autostart requires an existing configuration.
Impact
No unrelated collection or unauthorized account action was found in the reviewed flows.
Mechanism
Setup validates its Telegram token with Telegram's getMe endpoint. Model probes send a minimal ping with the configured provider key to that provider's configured endpoint.
AI rationale
The flagged command execution is part of an explicitly invoked setup utility, and its token check targets Telegram. Model probes send the configured provider key and a minimal ping to the configured provider endpoint; no unrelated credential destination or automatic install-time behavior was found.
Network endpoints2
api.telegram.org/bot<token>/getMe<configured provider base URL>/chat/completions
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes setup and check as explicit npm commands and declares no install lifecycle hook.
- Setup uses the Telegram bot token for a getMe request to api.telegram.org.
- Model probes send a one-token ping and the configured provider key to the profile's configured base URL.
- The plugin starts the bridge only when autostart is enabled, a config file exists, and no bridge is already running.
Evidence against
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
1 Critical6 High4 Medium5 Low
CriticalCommand Output Exfiltrationsetup.mjs#virtual:normalized:round1
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
LowScripts Present
Low
Affected versions and remediation
This report applies to dsh-tg-bridge@1.34.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.34.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.