ds-01@1.0.11
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe command’s dependency installation is part of its stated purpose, but interpolating registry-controlled values into `execSync` creates a concrete command-injection path. Because it requires a user-run add command and no exploit payload is established in the source, this is suspicious rather than clearly malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs the `ds01 add <component>` command, and the registry response includes a dependency missing from the project.
Impact
A crafted or compromised registry response could execute arbitrary commands with the CLI user’s privileges; npm may also run dependency install scripts.
Mechanism
Dependency strings from the response are joined and interpolated into `npm install ...` passed to `execSync`, allowing shell metacharacters in a returned value to execute commands.
AI rationale
The command’s dependency installation is part of its stated purpose, but interpolating registry-controlled values into `execSync` creates a concrete command-injection path. Because it requires a user-run add command and no exploit payload is established in the source, this is suspicious rather than clearly malicious.
Evidence
src/commands/add.tsdist/index.jspackage.jsonprocess.cwd()/config.componentsPath/componentName/*project package manifest and lockfile via npm install
Network endpoints1
ds-01.vercel.app
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The `add` command fetches component data from the DS01 registry endpoint.
- It takes dependency names from the registry response and filters out dependencies already listed in the project.
- It joins the remaining registry-provided values into a shell-interpolated `npm install` command executed with `execSync`.
- The `add` command is registered in the CLI, which parses user-supplied command arguments.
Evidence against
- The manifest declares no install, preinstall, or postinstall hook.
- Fetching a component and installing its dependencies are part of the CLI’s stated purpose, and the risky path runs inside the `add` action.
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.11.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.0.11 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.