@noob-stupid/dsh-plugin-console@0.5.106
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 6h ago · by lpm-firewall-aiThe repository lookup flow forwards a saved GitHub Bearer token to hard-coded third-party proxy hosts. This is credential disclosure to hosts outside GitHub, so the package is malicious.
Decision evidence
public snapshot- The package reads a GitHub token from `dshHome()/github-auth.json`.
- GitHub requests attach that token as a Bearer authorization header.
- GitHub API requests are also sent to hard-coded proxy mirrors, which receive the same request options, including the token.
- The `/repo` POST handler passes the stored token into a GitHub repository metadata request.
- The manifest describes a DSH plugin and framework upgrade console, consistent with the repository and plugin management features.
- The token-bearing request occurs in the repository lookup route rather than as an install or import-time action.
- The manifest’s only lifecycle hook runs a package.json BOM check.
Source & flagged code
19 flaggedPackage source references weak cryptographic algorithms.
lib/server/domain/install-verify.jsView on unpkg · L50Findings
Affected versions and remediation
This report applies to @noob-stupid/dsh-plugin-console@0.5.106.
See all versions of @noob-stupid/dsh-plugin-console for other recorded verdicts.
- Avoid installing @noob-stupid/dsh-plugin-console@0.5.106. 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.