Back to skill

Security audit

Seekit Search(No API Key Required)

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward guide for installing and using a live search tool, with ordinary supply-chain caution around its unpinned Python dependency.

Install seekit in a virtual environment or sandbox, consider pinning a reviewed version, and remember that search queries will be sent to whichever provider you select.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:12
Finding

Unpinned Third-Party Package Installation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 12-14
Vulnerability Type: Unpinned and unverified third-party dependency
Risk Level: Medium

Vulnerable Code:

bash
pip install seekit

Technical Analysis

The installation instructions retrieve the latest available version of the third-party seekit package from the Python package index configured in the user's environment. No exact version, cryptographic hash, lockfile, verified source repository, or publisher-validation procedure is specified.

Consequently, the installed artifact can change after this skill has been reviewed. If the package, its publishing account, the configured package index, or one of its transitive dependencies is compromised, a malicious release could execute code during installation or when the documented CLI or Python API is invoked. The package implementation is not included in this project, so its internal behavior cannot be independently verified from the audited contents.

Attack Path

  1. An attacker compromises the package publisher, package-index distribution path, or a transitive dependency and publishes a malicious release.
  2. A user or agent follows the documented pip install seekit instruction.
  3. Because no version or hash is pinned, pip resolves an attacker-controlled or otherwise unreviewed release.
  4. Malicious package installation logic or runtime code executes with the privileges of the user performing the installation.
  5. The payload may access resources available to that user, including local files, environment variables, credentials, and agent data.

Impact Assessment

Successful exploitation could result in arbitrary code execution under the installing user's account. The accessible scope would be limited by that account's operating-system permissions, environment isolation, and credential exposure. If installation is performed by a privileged account, the impact could extend to privi ...[truncated 259 chars]

Remediation
View remediation

Remediation Suggestions

  • Pin seekit to an exact, reviewed version rather than accepting the latest available release.
  • Record cryptographic hashes in a requirements file and install with:
    bash
    pip install --require-hashes -r requirements.txt
    
  • Pin and hash all transitive dependencies, preferably using a reproducible dependency-locking workflow.
  • Document and verify the package's official publisher, source repository, and release provenance.
  • Review package source and release changes before updating the pinned version.
  • Install the package in an isolated virtual environment or sandbox using a non-privileged account.
  • Configure trusted package indexes explicitly and avoid untrusted mirrors or extra indexes that could enable dependency confusion.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Static analysis

No suspicious patterns detected.