ds-01@1.0.13
Make your site best with DS01
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe add command has a command-injection flaw: registry-provided dependency values are passed through a shell without validation or argument-safe execution. This is a serious risk when the user invokes add, but the source does not show an active malicious payload, so the package is suspicious rather than malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the add command and the registry response includes dependencies missing from the project.
Impact
A crafted dependency value could execute arbitrary shell commands with the user's privileges in the project environment.
Mechanism
The package joins dependency values from the response and interpolates them into an npm install command executed through execSync.
AI rationale
The add command has a command-injection flaw: registry-provided dependency values are passed through a shell without validation or argument-safe execution. This is a serious risk when the user invokes add, but the source does not show an active malicious payload, so the package is suspicious rather than malicious.
Evidence
src/commands/add.tsdist/index.jsproject component files under config.componentsPath/componentNameproject package files and node_modules via npm install
Network endpoints1
ds-01.vercel.app/api/registry/{componentName} (or DS01_API_URL override)
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The add command uses the registry response's dependencies array as the source of packages to install.
- It joins those values into a shell command and passes the command to execSync, allowing shell metacharacters in a dependency value to execute arbitrary commands.
- The add command is registered as a CLI command and runs its action when invoked.
Evidence against
- The install path is part of the user-invoked add command, not a package lifecycle hook.
- The add command sends the DS01 token to the DS01 registry endpoint for the requested component.
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.13.
See all versions of ds-01 for other recorded verdicts.
- Review the evidence and your use of ds-01@1.0.13 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.