registry / dsh-tg-bridge / 1.19.4
dsh-tg-bridge@1.19.4
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-aiThe inspected credential flow uses the active profile’s configured provider destination and sends only a short probe request. The flagged agent-file write is tied to an explicit user command, and the package manifest has no install hook.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The bridge starts through its plugin or command entrypoint; provider probes run when requested by bridge logic; persona edits require a supplied /soul command.
Impact
No confirmed attack surface was established.
Mechanism
The probe sends a short ping with the configured provider key to the provider URL read from the active profile or its environment override. Persona text is written to the named agent file only after the explicit command supplies text.
AI rationale
The inspected credential flow uses the active profile’s configured provider destination and sends only a short probe request. The flagged agent-file write is tied to an explicit user command, and the package manifest has no install hook.
Evidence
AGENTS.md
Network endpoints1
api.telegram.org
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists ordinary command scripts and no install lifecycle hook; model probes load the active profile’s provider URL and key, then send a one-token ping to that provider.
- The agent persona file is edited only by the explicit /soul command when text is supplied; an empty command reads the current section.
- The inspected bridge and control operations handle bridge output, provider responses, plugin commands, and user-requested application controls.
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
2165try {
L2166: const drives = execFileSync('powershell', ['-NoProfile', '-NonInteractive', '-Command', '(Get-PSDrive C).Free'], {
L2167: 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.19.4.
See all versions of dsh-tg-bridge for other recorded verdicts.
- Review the evidence and your use of dsh-tg-bridge@1.19.4 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.