registry / dsh-tg-bridge / 1.38.6
dsh-tg-bridge@1.38.6
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe reviewed command and credential flows are tied to the package's stated Telegram bridge purpose and user-configured providers. The scanner's command-output exfiltration lead resolves to an explicit setup check against Telegram's own API, and no install lifecycle hook is declared.
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
Setup runs through an explicit command; probes follow provider fallback or diagnostics, and transcription follows a received audio attachment.
Impact
No malicious impact identified.
Mechanism
Commands manage the bridge. Network requests use Telegram's API or user-configured model and transcription providers; no unrelated credential collector or command-output exfiltration was found.
AI rationale
The reviewed command and credential flows are tied to the package's stated Telegram bridge purpose and user-configured providers. The scanner's command-output exfiltration lead resolves to an explicit setup check against Telegram's own API, and no install lifecycle hook is declared.
Network endpoints3
api.telegram.org/bot${botToken}/getMe${provider.baseUrl}/chat/completions${base}/audio/transcriptions
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares no install lifecycle hook; setup and check are explicit commands.
- setup reads the Telegram bot token and checks it against Telegram's own api.telegram.org getMe endpoint.
- The model probe uses the provider URL and key environment variable from the user's profile or explicit debug overrides, then sends a one-token ping to that provider.
- Audio transcription sends a received audio attachment and configured key to the configured speech 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 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.6.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.38.6 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.