T08 · Insecure Dependencies
- Location
SKILL.md:279- Finding
Unpinned Third-Party SDK Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:279
Vulnerability Type: Insecure dependency installation
Risk Level: MediumVulnerable Code Snippet:
markdown - **SDKs**: Python (`pip install crowterminal`), TypeScript (`npm install crowterminal`)Technical Analysis
The documentation recommends installing the
crowterminalpackages from public Python and npm registries without fixed versions, hashes, lockfiles, or integrity verification. Consequently, users following these commands will install whichever package release the registries resolve at installation time rather than a version reviewed with this Skill.Package installation can execute package-controlled build or lifecycle logic. The project file also does not provide evidence that the registry artifacts are reproducibly built from, or cryptographically tied to, the referenced source repository. This creates a supply-chain risk if a publisher account, package, registry, or future release is compromised.
Attack Path
- An attacker compromises the
crowterminalregistry package, its publisher account, or its release pipeline. - The attacker publishes a malicious version containing installation-time or runtime payloads.
- A user follows
SKILL.md:279and runspip install crowterminalornpm install crowterminal. - The package manager resolves and downloads the attacker-controlled current release.
- Malicious installation, build, lifecycle, import-time, or runtime code executes in the user's environment.
Impact Assessment
Successful exploitation could execute arbitrary code with the privileges of the user or automation account running the package manager. Depending on that environment, the payload could access application files, environment variables such as
CROWTERMINAL_API_KEY, developer credentials, creator data, and network-accessible services. It could also modify user-writable files or dependencies. No malici ...[truncated 134 chars]- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace floating installation commands with exact, reviewed versions, such as
crowterminal==X.Y.Zfor Python andcrowterminal@X.Y.Zfor npm. - Provide lockfiles and integrity metadata. For Python, publish a requirements file with cryptographic hashes and install with
pip --require-hashes. For npm, commit and use a reviewed lockfile withnpm ci. - Document the packages' verified official registry pages and their relationship to the referenced source repository.
- Verify package signatures, provenance attestations, and checksums where supported.
- Review package lifecycle and build scripts before adoption. Disable npm lifecycle scripts with
--ignore-scriptswhen they are not required. - Install dependencies in a least-privileged, isolated virtual environment or container, and avoid exposing unrelated credentials during installation.
- Establish an update-review process rather than allowing installations to resolve automatically to newly published releases.
- Replace floating installation commands with exact, reviewed versions, such as
