registry / dsh-tg-bridge / 1.7.2
dsh-tg-bridge@1.7.2
устаревшая сборка — ставьте 1.11.0 или новее
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 10d ago · by lpm-firewall-aiSource inspection found no install-time execution or separate credential receiver. The flagged behaviors are consistent with explicitly invoked setup and control commands and the package’s Telegram bridge function.
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
The user runs the bridge or setup command, or invokes a bridge control command.
Impact
No unintended disclosure, unrequested account action, or harmful configuration change was established.
Mechanism
The bridge communicates with Telegram, reads public model pricing data, edits a named persona section on command, and restarts its own process based on activity or delivery state.
AI rationale
Source inspection found no install-time execution or separate credential receiver. The flagged behaviors are consistent with explicitly invoked setup and control commands and the package’s Telegram bridge function.
Evidence
package.jsoncontrol.mjsbridge.mjsprices.mjssetup.mjsbridge-restart-idle.mjsrestart-after-send.mjs
Network endpoints2
api.telegram.orgmodels.dev
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes ordinary start and setup commands and contains no install lifecycle hook.
- control.mjs writes a named persona section in the user’s instructions file only through its explicit persona command.
- bridge.mjs reads the configured Telegram bot token and routes API calls to Telegram.
- prices.mjs uses the public models.dev catalog for model pricing.
- setup.mjs documents explicit setup and read-only check commands; the flagged helper scripts monitor turns and restart the bridge.
- The flagged restart helpers inspect bridge activity or delivery logs before restarting the local bridge.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggedsetup.mjsView file
19L20: import { spawnSync } from 'node:child_process';
L21: import { appendFileSync, existsSync, readFileSync, openSync, closeSync, unlinkSync, writeFileSync } from 'node:fs';
High
19L20: import { spawnSync } from 'node:child_process';
L21: import { appendFileSync, existsSync, readFileSync, openSync, closeSync, unlinkSync, writeFileSync } from 'node:fs';
...
L24:
L25: const DSH_HOME = process.env.DSH_HOME || join(homedir(), '.dsh');
L26: const BRIDGE_DIR = join(DSH_HOME, 'tg-bridge');
...
L48: let held = 0;
L49: try { held = Number(JSON.parse(readFileSync(LOCK, 'utf8')).pid) || 0; } catch {}
L50: let alive = false;
...
L63: /**
L64: * Every step is written to setup.log as well as stdout.
L65: *
High
Command Output Exfiltration
Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
setup.mjsView on unpkg · L19control.mjsView file
•matchType = previous_version_dangerous_delta
matchedPackage = dsh-tg-bridge@1.7.0
matchedIdentity = npm:ZHNoLXRnLWJyaWRnZQ:1.7.0
similarity = 0.792
summary = stored previous version shares package body but lacks this dangerous source file
Findings
2 Critical6 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
CriticalPrevious Version Dangerous Deltacontrol.mjs
HighChild Processsetup.mjs
HighShellcontrol.mjs
HighCommand Output Exfiltrationsetup.mjs
HighSemantic Analysis Limitedprices.mjs#virtual:normalized:round1
HighKnown Malware Source Similaritybridge-restart-idle.mjs
HighKnown Malware Source Similarityrestart-after-send.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpertranscribe.py
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to dsh-tg-bridge@1.7.2.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.7.2 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.