dsh-win32@0.17.6
Fix and diagnose DeepSeek Harness on native Windows. Official PowerShell, Workspace Write, shortcuts, and legacy preset repair. No WSL.
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection confirms that setup triggers an unrequested GitHub account change when an authenticated GitHub CLI session exists. This concrete behavior supports blocking the package.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs either setup flow outside CI.
Impact
The user's GitHub account is changed to star the publisher's repository.
Mechanism
The CLI calls offerSetupStar, which records a yes marker and uses the authenticated GitHub CLI to send a PUT request starring the repository.
Attack narrative
Running setup outside CI reaches the star helper without asking the user to confirm that account action. If the GitHub CLI has an authenticated account, the helper sends a request to star the publisher's repository and records a yes marker. The setup command does not establish consent for this separate, publisher-selected account change.
AI rationale
Source inspection confirms that setup triggers an unrequested GitHub account change when an authenticated GitHub CLI session exists. This concrete behavior supports blocking the package.
Evidence
bin/cli.mjsbin/setup-consent.mjs~/.dsh/.dsh-win32-star-prompted
Network endpoints1
github.com API: user/starred/sjh9714/dsh-win32
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json exposes bin/cli.mjs as the dsh-win32 command.
- Both setup flows call offerSetupStar after setup instructions.
- Outside CI, offerSetupStar proceeds to applySetupStar without a confirmation step.
- applySetupStar writes a marker containing “yes” before checking for an authenticated GitHub CLI session.
- When authenticated, the helper stars sjh9714/dsh-win32 through the GitHub API.
Evidence against
- The account change only proceeds when the GitHub CLI is authenticated; CI skips the action.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcebin/setup-consent.mjsView file
1import { execFileSync } from 'node:child_process'
L2: import { existsSync, mkdirSync, writeFileSync } from 'node:fs'
High
Child Process
Package source references child process execution.
bin/setup-consent.mjsView on unpkg · L1bin/cli.mjsView file
•matchType = previous_version_dangerous_delta
matchedPackage = dsh-win32@0.11.0
matchedIdentity = npm:ZHNoLXdpbjMy:0.11.0
similarity = 0.556
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/cli.mjsView on unpkg42if (process.env.ProgramFiles !== undefined) {
L43: const candidate = join(process.env.ProgramFiles, 'PowerShell', '7', 'pwsh.exe')
L44: if (existsSync(candidate)) return candidate
High
Shell
Package source references shell execution.
Findings
1 Critical5 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltabin/cli.mjs
HighChild Processbin/setup-consent.mjs
HighShellbin/cli.mjs
HighSame File Env Network Executionbin/cli.mjs
HighRuntime Package Installbin/cli.mjs
HighSemantic Analysis Limitedlib/index.d.ts#virtual:normalized:round1
MediumDynamic Requirebin/cli.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to dsh-win32@0.17.6.
See all versions of dsh-win32 for other recorded verdicts.
- Avoid installing dsh-win32@0.17.6. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.