registry / dsh-tg-bridge / 1.17.0
dsh-tg-bridge@1.17.0
Telegram bridge for DeepSeek Harness: text, voice, photos and project-per-topic sessions without opening the desktop app
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection found no npm lifecycle hook or confirmed attack behavior. The flagged global settings write is tied to an authenticated `/soul` command, while network requests use the configured Telegram service endpoint.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
A user starts the bridge or invokes one of its commands.
Impact
No unauthorized data transfer, installation-time mutation, or other confirmed attack impact was found.
Mechanism
The bridge sends Telegram API requests using its configured bot token; control commands check the sender against configured allowed IDs.
AI rationale
Source inspection found no npm lifecycle hook or confirmed attack behavior. The flagged global settings write is tied to an authenticated `/soul` command, while network requests use the configured Telegram service endpoint.
Evidence
control.mjsbridge.mjs
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines no npm install lifecycle hook; setup and hook installation are named commands.
- The global persona file is changed only by the `/soul` command, and the bridge checks the sender against configured allowed user IDs.
- The bridge builds its API URL for api.telegram.org using the configured Telegram bot token; inspected network calls serve the bridge’s Telegram messaging and file-transfer functions.
- Flagged runtime locations resolve to local media processing, log formatting, settings, profile, plugin, restart, and session-control operations.
- The remaining flagged files implement settings-card rendering, surgical profile edits, an explicitly invoked Git secret-scanning hook installer, and bridge setup or restart utilities.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
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
control.mjsView file
1931try {
L1932: const drives = execFileSync('powershell', ['-NoProfile', '-NonInteractive', '-Command', '(Get-PSDrive C).Free'], {
L1933: encoding: 'utf8',
High
•Manifest-trigger-reachable source links an external AI-agent control path to a behavior-bearing write operation.
ed') }));
}
function sessiontitle(id) {
const record = readjson(join(dsh_home, 'storages', 'session_projcache', 'sessions', `session-${bareid(id)}.json`));
const rows = record?.record?.rows ?? record?.rows ?? {};
const title = rows.title?.val;
if (typeof title === 'string' && title.trim()) return title.trim();
const first = rows.titleinput?.val?.first?.text;
if (typeof first === 'string' && first.trim()) return first.tr
Findings
1 Critical7 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationbridge.mjs
HighChild Processinstall-hooks.mjs
HighShellcontrol.mjs
HighCommand Output Exfiltrationsetup.mjs
HighTrigger Reachable External Ai Agent Control Surface Mutationcontrol.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
Low
Affected versions and remediation
This report applies to dsh-tg-bridge@1.17.0.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.17.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.