registry / dsh-tg-bridge / 1.33.3
dsh-tg-bridge@1.33.3
Drive DeepSeek Harness from Telegram: one project, model and session per forum topic
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s inspected network and process behavior supports its stated Telegram bridge purpose. Provider credentials are sent to the profile-configured provider, and setup checks the Telegram bot token against Telegram’s official API; no install-time exfiltration or unrelated automatic action 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
Setup is run by the user; provider probes run during fallback diagnostics; the bridge plugin starts only when configured and enabled.
Impact
The inspected behavior supports Telegram bridge operation and provider availability checks; no unrelated data collection or unauthorized account action was found.
Mechanism
Inspected network requests target Telegram’s getMe endpoint or the provider base URL configured in the user’s profile, and the model probe uses that provider’s configured key.
AI rationale
The package’s inspected network and process behavior supports its stated Telegram bridge purpose. Provider credentials are sent to the profile-configured provider, and setup checks the Telegram bot token against Telegram’s official API; no install-time exfiltration or unrelated automatic action was found.
Evidence
package.jsonmodel-probe.mjsfallback.mjssetup.mjsplugin-bridge.mjs
Network endpoints2
api.telegram.orgProfile-configured provider base URL
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest defines no install, preinstall, or postinstall lifecycle scripts; its main entry is the Telegram bridge plugin.
- Model probes use the base URL and key environment variable configured for the selected provider profile.
- A model probe sends a one-token ping to that provider’s /chat/completions endpoint using its configured key.
- The setup script’s network check calls Telegram’s official api.telegram.org getMe endpoint with the bot token.
- The plugin starts the bridge only when autoStart is enabled, a configuration file exists, and no bridge process is already running.
Evidence against
- The package includes process execution, filesystem access, and network requests, but the inspected paths show setup, bridge management, and provider diagnostics consistent with the package’s stated purpose.
- The model probe reads a provider key from its configured environment variable or DSH credentials file; the inspected request sends it to the profile-configured provider.
Behavioral surface
ChildProcessCrypto
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/cmd-bridge.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.3.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.33.3 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.