ds-01@1.0.8
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe `add` command passes registry-controlled dependency data to a shell without safe argument separation, creating a real remote command-injection risk. The inspected source does not show an active malicious payload, so this is a critical vulnerability rather than confirmed malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI `add` command and the registry response includes dependencies.
Impact
A crafted registry response could execute arbitrary shell commands with the user's privileges; the inspected source does not establish that the server is currently returning malicious data.
Mechanism
The command joins returned dependency strings and interpolates them into `execSync` as `npm install ${depsToInstall}`.
AI rationale
The `add` command passes registry-controlled dependency data to a shell without safe argument separation, creating a real remote command-injection risk. The inspected source does not show an active malicious payload, so this is a critical vulnerability rather than confirmed malicious behavior.
Evidence
dist/commands/add.js${cwd}/${config.componentsPath}/${componentName}/${file.name}
Network endpoints1
ds-01.vercel.app/api/registry/${componentName} (default; overridable with DS01_API_URL)
Decision evidence
public snapshotAI called this Suspicious at 96.0% confidence as Critical Vulnerability with medium false-positive risk.
Evidence for warning
- The `add` command takes dependency names from the registry response and joins them into a shell command.
- It runs `npm install ${depsToInstall}` with `execSync`, which invokes a shell and permits command injection through the registry-supplied value.
- The request uses the DS01 registry endpoint and sends the DS01 session token; no unrelated credential destination was identified.
Evidence against
- The package has no install lifecycle scripts; its CLI is exposed as a command-line binary.
- The risky command runs only when a user invokes `add` and the registry response includes dependencies.
- The default registry host is `ds-01.vercel.app`, consistent with the package’s stated component-registry purpose.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
UrlStrings
Source & flagged code
6 flaggeddist/utils/secureKeyStore.jsView file
1// cli/src/utils/secureKeyStore.ts
L2: import { execFile } from "node:child_process";
L3: import { promisify } from "node:util";
High
Child Process
Package source references child process execution.
dist/utils/secureKeyStore.jsView on unpkg · L164`;
L65: const { stdout } = await execFileAsync("powershell.exe", [
L66: "-NoProfile",
High
dist/commands/add.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = ds-01@0.1.5
matchedIdentity = npm:ZHMtMDE:0.1.5
similarity = 0.533
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.
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/commands/add.js
HighChild Processdist/utils/secureKeyStore.js
HighShelldist/utils/secureKeyStore.js
HighSame File Env Network Executiondist/commands/add.js
HighRuntime Package Installdist/commands/add.js
HighSemantic Analysis Limiteddist/commands/login.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to ds-01@1.0.8.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.0.8 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.