registry / dsh-tg-bridge / 1.35.0
dsh-tg-bridge@1.35.0
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged shell and credential behavior serves the package's stated bridge, setup, model-probe, and transcription functions. The reviewed credential flows send tokens to Telegram or user-configured providers; I found no unrelated collector or concealed automatic action.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The user runs setup or invokes configured bridge features; plugin startup also requires an existing config and enabled autoStart.
Impact
No unauthorized collection, unrelated credential transfer, or hidden account action was identified.
Mechanism
Uses Telegram's API for bot operations and configured provider or transcription endpoints for model and audio requests.
AI rationale
The flagged shell and credential behavior serves the package's stated bridge, setup, model-probe, and transcription functions. The reviewed credential flows send tokens to Telegram or user-configured providers; I found no unrelated collector or concealed automatic action.
Network endpoints3
api.telegram.orgconfigured provider.baseUrlconfigured voice.baseUrl
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines no npm lifecycle hooks; setup, check, and hooks are explicitly invoked scripts.
- The plugin starts the bridge only when autoStart is enabled, a config file exists, and no bridge process is already running.
- Setup uses the Telegram bot token to call Telegram's own getMe endpoint as a connectivity check.
- Model probes send a minimal ping and the provider key to the base URL configured in the user's profile.
- Voice transcription sends audio to the configured speech endpoint when transcription is requested.
Evidence against
- Setup reads the Telegram token and runs system commands, but the reviewed code uses them for bridge diagnostics, restart, and scheduling.
- The bridge reads configured provider credentials; the reviewed probe sends them to the configured provider host.
- The package can write a global persona file, but the write is reached through an explicit /soul command.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
Source & flagged code
9 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
1 Critical6 High4 Medium5 Low
CriticalCommand Output Exfiltrationsetup.mjs#virtual:normalized:round1
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
LowScripts Present
Low
Affected versions and remediation
This report applies to dsh-tg-bridge@1.35.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.35.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.