Security audit

yandex-tracker

Security checks for vulnerabilities and agentic risk

Overview

This skill is a clearly scoped Yandex Tracker integration, with sensitive actions disclosed and tied to user authorization.

Install this only in an environment where you are comfortable letting the agent use a Yandex Tracker token. Use a least-privilege token, avoid broad admin scopes, confirm issue sets before bulk changes, and pin or review the Python dependency before installation when possible.

A.I.G

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:14
Finding: Unpinned Third-Party Python Dependency
Content: View full analysis
Remediation: View remediation
``` ```bash python -m pip install "yandex_tracker_client==" ``` 2. Use a lock file or requirements file containing cryptographic hashes, and install with hash verification: ```bash python -m pip install --require-hashes -r requirements.txt ``` 3. Generate hashes from trusted release artifacts and verify the package's publisher, repository, and release provenance before approving upgrades. 4. Perform dependency updates through an explicit review process rather than automatically tracking the latest release. 5. Run package installation and Tracker operations in an isolated, least-privilege environment with restricted filesystem and network access. 6. Continue using a least-privilege Tracker token so a dependency compromise cannot exceed the permissions required for the requested operation. 7. Keep the dependency declaration in `SKILL.md`, installation command in `README.md`, and any lock or requirements file synchronized. ]]>

SkillSpector

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