dsh-win32@0.17.8
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-aiThe setup flow performs a publisher-selected authenticated account action without an affirmative consent step. This is concrete attack behavior and supports blocking despite requiring explicit setup invocation.
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 a CI environment with an authenticated GitHub CLI account.
Impact
The user's GitHub account is modified without recipient-specific consent.
Mechanism
The setup helper records an affirmative marker and sends an authenticated GitHub API request to star the repository.
Attack narrative
Running setup outside CI can cause the package to use an existing GitHub CLI login to star the publisher's repository. The helper records an affirmative marker without asking first, and the CI check is the only guard shown.
AI rationale
The setup flow performs a publisher-selected authenticated account action without an affirmative consent step. This is concrete attack behavior and supports blocking despite requiring explicit setup invocation.
Evidence
package.jsonbin/cli.mjsbin/setup-consent.mjs~/.dsh/.dsh-win32-star-prompted
Network endpoints1
github.com
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package scripts define build and test tasks, with no preinstall, install, or postinstall hook.
- Both setup flows call the star helper automatically at the end of setup.
- Outside CI, the helper writes a marker recording an affirmative answer before checking for an authenticated GitHub account; no consent prompt is shown in this flow.
- When GitHub CLI authentication is available, the helper uses that account to star the publisher-selected repository.
- The only explicit guard skips the action in CI environments.
Evidence against
- The action requires a user to invoke a setup command, and CI environments skip it.
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.8.
See all versions of dsh-win32 for other recorded verdicts.
- Avoid installing dsh-win32@0.17.8. 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.