ds-01@1.0.12
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe component-add flow has a real command-injection risk: registry-provided dependency values are interpolated into a shell command without validation. Because this is a user-triggered feature and the source does not show an actual malicious registry response, classify it as suspicious rather than malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs `ds01 add <component>` and the registry returns missing dependencies or file names containing crafted values.
Impact
A crafted dependency value could execute arbitrary shell commands with the user's privileges. A crafted file name could write outside the component directory.
Mechanism
Dependency strings are joined and interpolated into `execSync('npm install ...')`; file names are joined to the configured component directory without containment checks.
AI rationale
The component-add flow has a real command-injection risk: registry-provided dependency values are interpolated into a shell command without validation. Because this is a user-triggered feature and the source does not show an actual malicious registry response, classify it as suspicious rather than malicious.
Evidence
src/commands/add.tscwd/config.componentsPath/componentName/file.namecwd/package.jsonnode_modules/
Network endpoints1
ds-01.vercel.app
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The explicit `add` command takes dependencies from the registry response and interpolates them into an `execSync` shell command without validating the values, allowing a malicious response to inject shell commands.
- Registry-provided file names are joined to the component target directory without checking that the resulting paths stay inside it.
Evidence against
- The CLI’s stated purpose is to fetch DS01 components and their dependencies; this behavior runs only when the user invokes `add`.
- The manifest defines no install, preinstall, or postinstall hook; its only script is a build command.
- The default registry host is `ds-01.vercel.app`; the API URL can be overridden through `DS01_API_URL`.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
UrlStrings
NoLicense
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 · L171`;
L72: const { stdout } = await execFileAsync("powershell.exe", [
L73: "-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
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.12.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.0.12 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.