registry / Remote code execution / ds-01
ds-01
Make your site best with DS01
This report shows the evidence for ds-01@1.0.9. 1 of 14 known versions is blocked or flagged. The newest version, 1.1.1, is flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe add flow turns registry-controlled dependency data into a shell command without validation, creating a direct remote command execution path. The flow requires an explicit add command, but the registry response can execute commands beyond the requested dependency installation.
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 shell metacharacters in its dependency list.
Impact
An attacker controlling or compromising the registry response could run arbitrary commands with the user's privileges.
Mechanism
The CLI joins returned dependency strings and interpolates them into a shell-based `npm install` command.
Attack narrative
When a user adds a component, the CLI fetches registry data and passes its dependency list to `execSync` as an interpolated shell command. A crafted response can break out of the intended npm install command and execute arbitrary commands with the user's privileges.
AI rationale
The add flow turns registry-controlled dependency data into a shell command without validation, creating a direct remote command execution path. The flow requires an explicit add command, but the registry response can execute commands beyond the requested dependency installation.
Evidence
src/commands/add.tsprocess.cwd()/config.componentsPath/componentName/file.namenpm project files modified by npm install
Network endpoints1
ds-01.vercel.app
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The `add` command fetches component data from the DS01 registry and parses the response as JSON.
- The command joins server-returned dependency values and interpolates them into `execSync('npm install ...')`, which invokes a shell without validating the values.
- A crafted registry response can therefore execute arbitrary shell commands when a user adds a component.
Evidence against
- The risky flow runs only after a user invokes the `add` command.
- Installing component dependencies is part of the CLI’s stated purpose, and the default registry is the package’s DS01 service.
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 · L134*
L35: * Node -> PowerShell -> Windows crypto provider
L36: * ↓
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.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing ds-01@1.0.9. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.