T08 · Insecure Dependencies
- Location
SKILL.md:22- Finding
Unpinned Third-Party Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:22-26
Vulnerability Type: Supply-chain exposure through an unpinned dependency
Risk Level: Mediumbash pip install scraplingTechnical Analysis
The installation instructions retrieve and install whichever version of
scraplingis current at execution time. No reviewed version, package hash, lock file, or trusted index configuration is specified. Consequently, the code installed by users may differ from the code reviewed during this audit.This does not establish that the current dependency is malicious. However, it creates a supply-chain trust gap: a compromised upstream account, malicious future release, dependency takeover, or unexpected package resolution could introduce arbitrary installation-time or runtime behavior.
Attack Path
- An attacker compromises the upstream package, its publishing credentials, or a transitive dependency.
- The attacker publishes a malicious package release.
- A user follows the documented
pip install scraplinginstruction. - Package installation or import executes attacker-controlled code in the user's Python environment.
- That code operates with the privileges of the user running the installation or Skill.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's privileges. Depending on the environment, this could expose Boss Zhipin authentication cookies, candidate resume data, environment variables, local files accessible to the user, and network credentials. The Skill itself does not request administrative privileges, so the direct scope is limited to the installing user's permissions unless the installation command is run with elevated privileges.
- Remediation
View remediation
Remediation Suggestions
- Pin
scraplingto a specifically reviewed version. - Maintain a lock file covering all transitive dependencies.
- Require package hashes, such as through
pip install --require-hashes. - Configure installation to use an explicitly trusted package index.
- Run dependency vulnerability and provenance checks in CI.
- Install dependencies inside a dedicated virtual environment or restricted container.
- Avoid running package installation with administrative privileges.
- Pin
