registry / dsh-tg-bridge / 1.38.2
dsh-tg-bridge@1.38.2
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe flagged command execution, credential use, and network calls serve explicit setup, bridge, transcription, or configured model-probe functions. I found no install hook or unrelated collection or execution path.
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 CLI setup is user-run; the plugin may start a configured bridge when the host loads it.
Impact
No unrelated data transfer or harmful action was identified in the inspected flows.
Mechanism
The bridge uses Telegram’s API and sends audio or model-probe requests to configured provider endpoints with their corresponding keys.
AI rationale
The flagged command execution, credential use, and network calls serve explicit setup, bridge, transcription, or configured model-probe functions. I found no install hook or unrelated collection or execution path.
Network endpoints4
api.telegram.orgapi.openai.comvoice.baseUrlprovider.baseUrl
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 has no install lifecycle hook; setup is an explicit npm script, and the package entry points are the plugin and CLI.
- Speech transcription sends the supplied audio and configured key to the configured voice endpoint; the default is OpenAI’s API.
- Model probes read the configured provider key and send it to that provider’s configured base URL for a one-token completion.
- The setup check calls Telegram’s getMe endpoint with the Telegram bot token, consistent with the bridge’s stated purpose.
- The plugin starts the bridge only when a config file exists and auto-start has not been disabled.
Evidence against
- The source includes process execution, filesystem access, persistence helpers, and network calls, but the inspected uses support setup, bridge restarts, and Telegram operation.
- I found no unrelated credential collection, command-output exfiltration, concealed payload execution, or unrequested account actions.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
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 Deltachat/media.mjs
HighChild Processinstall-hooks.mjs
HighShellsetup.mjs#virtual:normalized:round1
HighSame File Env Network Executionsetup.mjs#virtual:normalized:round1
HighSemantic Analysis Limitedchat/media.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritywork/bridge-restart-idle.mjs
HighKnown Malware Source Similaritywork/restart-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.38.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.38.2 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.