registry / dsh-tg-bridge / 1.12.0
dsh-tg-bridge@1.12.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 lifecycle hooks or concrete malicious behavior; the network calls inspected target Telegram for the package’s stated bridge function. Scanner hints about external exfiltration and agent configuration were not supported by the inspected source behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The user starts the bridge or invokes one of its Telegram commands.
Impact
No confirmed unauthorized data transfer, persistence, or agent control change was established.
Mechanism
The bridge polls Telegram and uses its Bot API to process and reply to messages; setup checks the configured bot token with Telegram.
AI rationale
Source inspection found no install lifecycle hooks or concrete malicious behavior; the network calls inspected target Telegram for the package’s stated bridge function. Scanner hints about external exfiltration and agent configuration were not supported by the inspected source behavior.
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines ordinary start and setup commands and no install lifecycle hooks.
- bridge.mjs sends bridge API requests to Telegram’s Bot API, which matches the package’s stated purpose.
- The agent persona file is written through a control-plane helper; the inspected caller exposes it as a user command.
- setup.mjs validates the supplied bot token through Telegram’s Bot API.
- The flagged control, panel, pricing, profile, and restart code is consistent with Telegram controls, status display, user-requested price lookup, profile editing, and bridge restart behavior.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 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
1620try {
L1621: const drives = execFileSync('powershell', ['-NoProfile', '-NonInteractive', '-Command', '(Get-PSDrive C).Free'], {
L1622: encoding: 'utf8',
Findings
1 Critical6 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
HighChild Processsetup.mjs
HighShellcontrol.mjs
HighCommand Output Exfiltrationsetup.mjs
HighSemantic Analysis Limitedpanel.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
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to dsh-tg-bridge@1.12.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.12.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.