registry / dsh-tg-bridge / 1.31.1
dsh-tg-bridge@1.31.1
Telegram bridge for [DSH]: 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 output is used for local setup status, while the model probe sends a configured provider key to that provider’s configured URL only after model failures. The package’s startup and setup behavior fits its declared Telegram bridge purpose.
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 after initialization, model fallback after a provider failure, or an explicit setup command.
Impact
Expected bridge operation; no unrelated data collection or attacker-chosen account actions were identified.
Mechanism
The bridge uses configured credentials with their intended Telegram or model-provider services. Setup’s command output is used locally for status and logging.
AI rationale
The flagged command output is used for local setup status, while the model probe sends a configured provider key to that provider’s configured URL only after model failures. The package’s startup and setup behavior fits its declared Telegram bridge purpose.
Evidence
${DSH_HOME}/tg-bridge/config.json${DSH_HOME}/tg-bridge/setup.log${DSH_HOME}/tg-bridge/bridge-kick-hidden.vbs
Network endpoints2
api.telegram.org/bot{botToken}/getMe{profile-configured provider.baseUrl}/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 describes a Telegram bridge and declares no install lifecycle scripts.
- The plugin starts the bridge only when enabled and after initialization has created its config file.
- The model probe uses a provider URL and key selected from the DSH profile or explicit environment overrides; fallback code invokes it after model failures.
- Setup’s token check calls Telegram’s official 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 Deltacontrol/release.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.31.1.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.31.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.