registry / dsh-tg-bridge / 1.39.0
dsh-tg-bridge@1.39.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe flagged command execution and network calls serve the Telegram bridge’s setup and runtime functions. Reviewed credential requests use configured provider endpoints, and setup’s token check targets Telegram’s official API; no concrete attack behavior 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
Bridge startup or an explicit setup, model probe, or configured media transcription action.
Impact
No malicious impact identified in the reviewed source.
Mechanism
Uses Telegram’s API with the configured bot token and sends provider credentials only with requests to configured provider endpoints.
AI rationale
The flagged command execution and network calls serve the Telegram bridge’s setup and runtime functions. Reviewed credential requests use configured provider endpoints, and setup’s token check targets Telegram’s official API; no concrete attack behavior was found.
Network endpoints3
api.telegram.orgapi.openai.com/v1provider.baseUrl (configured)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package describes itself as a Telegram bridge for DeepSeek Harness.
- The plugin starts the bridge only after a config file exists.
- Model probes send a one-token ping to the base URL configured for that provider, using its associated key.
- Setup checks the bot token by calling Telegram’s official getMe endpoint.
Evidence against
- The flagged shell and process execution support bridge setup, restart, and configured local transcription.
- The inspected credential flows send keys to their configured provider endpoints; no unrelated credential collector was identified.
- No preinstall, install, or postinstall script is declared.
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 Deltaturn/turn.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.39.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.39.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.