ds-01@1.0.5
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s add flow contains a real command-injection vulnerability: registry-provided dependency values are passed to a shell without validation. The flow requires an explicit add command, so this is a critical vulnerability rather than evidence of an automatic attack.
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 response includes dependencies.
Impact
Crafted registry data could execute arbitrary commands with the user's privileges in the project environment.
Mechanism
The CLI joins the returned dependency values and inserts them into `npm install` passed to `execSync`, which invokes a shell.
AI rationale
The package’s add flow contains a real command-injection vulnerability: registry-provided dependency values are passed to a shell without validation. The flow requires an explicit add command, so this is a critical vulnerability rather than evidence of an automatic attack.
Evidence
dist/commands/add.jspath.join(cwd, config.componentsPath, componentName, file.name)project working directory via npm install
Network endpoints2
ds-01.vercel.app/api/registry/${componentName}process.env.DS01_API_URL/api/registry/${componentName}
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 fetches a component registry response and reads its JSON body.
- It joins registry-provided dependency values and interpolates them into a shell command, creating a command-injection path if the response contains crafted values.
Evidence against
- The risky path runs only when a user invokes the `add` command; the package has no install lifecycle hook.
- The CLI’s default registry host is its stated DS01 service, and adding components and their dependencies is part of the package’s purpose.
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 · 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.5.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.0.5 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.