registry / dsh-tg-bridge / 1.33.0
dsh-tg-bridge@1.33.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package has no install lifecycle hook in its declared scripts. The flagged credential flow sends a configured provider key to that provider's configured endpoint during fallback checks, while setup's token check targets Telegram's official API.
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
Explicit CLI commands, or plugin startup after runtime configuration exists.
Impact
No malicious impact identified in the inspected source.
Mechanism
The bridge can probe a configured model provider with a one-token request after route failures, and setup validates the configured bot token with Telegram.
AI rationale
The package has no install lifecycle hook in its declared scripts. The flagged credential flow sends a configured provider key to that provider's configured endpoint during fallback checks, while setup's token check targets Telegram's official API.
Evidence
~/.dsh/tg-bridge/~/.dsh/.credentials.yaml
Network endpoints2
api.telegram.org/bot${botToken}/getMe${provider.baseUrl}/chat/completions (provider base URL comes from profile configuration)
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes explicit start, setup, and check scripts; package.json declares no install lifecycle hook.
- The model probe reads a key named by the provider profile and sends it to that provider's configured base URL.
- Fallback model probing is reached while handling model-route failures.
- The plugin starts the bridge only when its runtime config file exists and no bridge is already running.
- Setup validates the configured bot token against Telegram's official getMe API.
Evidence against
- Credential use in the inspected flow is tied to a configured model provider, not an unrelated collector.
- The observed startup and network behavior matches the package's Telegram bridge and model fallback purpose.
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.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.33.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.33.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.