registry / @noob-stupid/dsh-plugin-console / 0.5.45
@noob-stupid/dsh-plugin-console@0.5.45
DSH 框架升级安全与插件升级门控：一键升级、失败自动回滚、升级后回滚上版、旧插件不适配自动禁用；内置多源插件市场为发现层，插件源全部可自定义，可指向公司内网私有源 / 私有索引 / 本地 Git 仓库，纯内网离线可用 | Framework upgrade safety & plugin version gating for DSH, with a customizable multi-source plugin market: point every source at internal mirror
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest’s only lifecycle-like script is prepublishOnly, which runs a BOM check. The flagged persistence behavior is tied to framework upgrade or rollback routes, while install diagnosis does not automatically expand build-script approvals.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the framework upgrade or rollback flow.
Impact
No confirmed attack surface was established by the inspected source.
Mechanism
Those routes generate PowerShell scripts to perform the requested operation; the package has no install lifecycle hook that launches them automatically.
AI rationale
The manifest’s only lifecycle-like script is prepublishOnly, which runs a BOM check. The flagged persistence behavior is tied to framework upgrade or rollback routes, while install diagnosis does not automatically expand build-script approvals.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines only a BOM-checking prepublishOnly hook; no install lifecycle hook is present.
- The rollback route writes and launches a PowerShell script as part of its rollback flow.
- The framework upgrade route creates a PowerShell script for its upgrade flow.
- Non-Windows systems are refused the one-click upgrade and rollback path.
- Install diagnosis says it only presents build-script approval guidance and does not write the allowBuilds policy.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedlib/server/domain/install-verify.jsView file
50try {
L51: const manifest = JSON.parse(readFileSync(join(profileDir, 'package.json'), 'utf8'))
L52: const bundles = manifest?.dsh?.profile?.bundles
Low
Weak Crypto
Package source references weak cryptographic algorithms.
lib/server/domain/install-verify.jsView on unpkg · L50lib/server/domain/framework.jsView file
4Trigger-reachable persistence chain: manifest.main -> lib/index.js -> lib/server/domain/framework.js
L4: import { readFileSync, writeFileSync, existsSync, readdirSync, mkdirSync, copyFileSync } from 'node:fs'
L5: import { execFile } from 'node:child_process'
L6: import { dirname, join, basename, resolve } from 'node:path'
...
L18: try {
L19: const requireLocal = createRequire(join(pluginRoot(), 'package.json'))
L20: return join(dirname(requireLocal.resolve('@deepseek-ai/dsh/package.json')), 'lib', 'bin.js')
...
L31: * npm 的 cache 位置本来就是用户配置（把 cache 指到别的盘是常见做法），所以按 npm 自己的
L32: * 配置来源读取：环境变量 npm[redacted] / NPM_CONFIG_CACHE，以及用户级 ~/.npmrc 的 `cache=`。
L33: * （原实现把开发机上某个盘符下的 `node_cache\_npx` 直接写进源码，随 npm 发给所有用户。） */
...
L37: if (typeof value !== 'string') return
L38: const dir = value.tri
High
Findings
2 Critical2 High4 Medium6 Low
CriticalPersistence Backdoorlib/server/routes/framework.js
CriticalTrigger Reachable Dangerous Capabilitylib/server/routes/framework-upgrade.js
HighTrigger Reachable Persistencelib/server/domain/framework.js
HighSemantic Analysis Limitedlib/server/domain/install-diagnose.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencelib/server/domain/framework.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptolib/server/domain/install-verify.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to @noob-stupid/dsh-plugin-console@0.5.45.
See all versions of @noob-stupid/dsh-plugin-console for other recorded verdicts.
- Review the evidence and your use of @noob-stupid/dsh-plugin-console@0.5.45 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.