registry / dsh-tg-bridge / 1.5.3
dsh-tg-bridge@1.5.3
устаревшая сборка — ставьте 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 11d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged setup, Telegram API, restart, and agent-configuration behavior is consistent with user-invoked bridge operation and control commands.
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 bridge starts when invoked by its CLI, plugin, or setup flow; control changes require a matching Telegram command.
Impact
The inspected behavior supports the advertised bridge and user-requested controls; no unrelated credential transfer or unconsented agent configuration change was established.
Mechanism
The bridge reads its Telegram bot token from DSH credentials or the environment and calls the Telegram API. Recognized commands pass their arguments to control handlers; the persona command writes supplied text to the DSH instructions file.
AI rationale
Source inspection found no install lifecycle hook or concrete attack behavior. The flagged setup, Telegram API, restart, and agent-configuration behavior is consistent with user-invoked bridge operation and control commands.
Evidence
bridge.mjscontrol.mjssetup.mjsbridge-restart-idle.mjsrestart-after-send.mjs
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines start, setup, and check commands but no install lifecycle hook; the package has no dependencies.
- bridge.mjs reads the Telegram bot token from its environment or DSH credentials and builds API requests for Telegram.
- The bridge passes recognized Telegram command arguments to its control handler; plugin changes use the supplied action and value.
- The /soul command writes user-provided text to the DSH persona section; the agent-configuration write is command-triggered.
- setup.mjs probes Telegram with getMe using the bot token as part of setup diagnostics.
- The restart helpers wait for an idle bridge or a delivered reply before restarting it.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 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 · L19bridge.mjsView file
7Source sends the broad process environment to a literal external destination.
L7: // the logon task (see README.md).
L8: import { spawn } from 'node:child_process';
L9: import {
...
L19: // 5.3 s, IPv6 to GitHub 0.02 s refused). The --dns-result-order flag alone
L20: // does not bind fetch/undici, so pin the family on the socket layer.
L21: import dns from 'node:dns';
L22: import net from 'node:net';
...
L32:
L33: const HOME = homedir();
L34: const DSH_HOME = process.env.DSH_HOME || join(HOME, '.dsh');
L35: // State, config and logs live here. DSH_TG_HOME lets a checkout run with its own
...
L115: try {
Findings
2 Critical4 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
CriticalPrevious Version Dangerous Deltacontrol.mjs
HighChild Processsetup.mjs
HighCommand Output Exfiltrationsetup.mjs
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
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.5.3.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.5.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.