T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unverified Python Package Presented as an Official Sentry CLI Installation Option
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 4 and 15
Vulnerability Type: Supply-chain risk through an unverified third-party dependency
Risk Level: MediumVulnerable Code Snippets
Metadata declaration at line 4:
yaml metadata: {"openclaw":{"requires":{"bins":["sentry-cli"]},"install":[{"id":"npm","kind":"npm","package":"@sentry/cli","global":true,"bins":["sentry-cli"],"label":"Install sentry-cli (npm)"},{"id":"pip","kind":"pip","package":"sentry-cli","bins":["sentry-cli"],"label":"Install sentry-cli (pip)"}]}}Installation instruction at line 15:
bash pip install sentry-cliTechnical Analysis
The Skill presents the unscoped PyPI package
sentry-clias an interchangeable alternative to the explicitly scoped npm package@sentry/cli. It provides no publisher verification, provenance information, exact version pin, package hash, signature validation, or other integrity control for the Python package.Installing a package can execute package-controlled installation or build logic. The resulting
sentry-cliexecutable is then trusted by the Skill and may run while sensitive Sentry environment variables are available. A malicious, compromised, dependency-confused, or unrelated package could therefore execute arbitrary code under the installing user's account.This is a confirmed insecure dependency instruction. It does not establish that the current PyPI package is malicious; the vulnerability is the recommendation to install and trust it without demonstrating authoritative provenance or applying integrity protections.
Attack Path
- A user or agent follows the documented Python installation alternative.
pipresolves the mutable package namesentry-clifrom the configured Python package index.- A compromised, spoofed, or otherwise untrusted release supplies package-controlled code.
- Code may execute during installation or when the generated
sentry-clicommand is invoked. - The executable ...[truncated 1177 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
pip install sentry-clioption unless the package's authoritative ownership and equivalence to Sentry's official CLI can be established. - Prefer Sentry's officially documented distribution channel and link to the authoritative installation documentation.
- Pin the dependency to a reviewed exact version rather than resolving an unconstrained mutable version.
- Verify package integrity with publisher signatures, trusted provenance attestations, or cryptographic hashes where supported.
- Avoid global installation where possible. Use an isolated environment or a project-local, lockfile-controlled tool dependency.
- Configure package managers to use trusted registries and enforce dependency provenance policies.
- Review release notes and package ownership before upgrades, and perform periodic supply-chain scanning.
- Use narrowly scoped, short-lived Sentry tokens so a compromised CLI cannot obtain broader access than necessary.
- Remove the
