T08 · Insecure Dependencies
Warning
- Location
README.md:19- Finding
Unpinned Third-Party Dependencies and Browser Artifacts
- Content
View full analysis
- Remediation
View remediation
Security audit
Yandex Archive Scraper
Security checks for vulnerabilities and agentic risk
Overview
This is a disclosed Yandex.Archive scraper, but it explicitly uses stealth tooling to bypass bot protection without clear authorization or rate-limit guardrails.
Review this before installing. Use it only where you have authorization to access and scrape the target service, set conservative page limits and delays, and respect applicable terms and robots/rate-limit expectations. Install dependencies in a dedicated virtual environment or container because the package list and browser download are not pinned or hash-verified.
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)
Vulnerability Patterns
- Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
- MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (6)
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
The README explicitly promotes use of Scrapling/StealthyFetcher to bypass bot protection and Cloudflare Turnstile, which is a capability associated with evading access controls rather than normal interoperability. In an agent skill context, this increases the chance the tool will be deployed for unauthorized large-scale scraping or policy-violating access without any warning, restrictions, or compliance guidance.
- Content
Undeclared Tool Scope
Medium
- Category
- MCP Least Privilege
- Confidence
- 95% confidence
- Finding
The skill advertises network-enabled scraping behavior but does not declare any explicit tool scope or allowed-tools boundary. That omission weakens least-privilege controls and makes it harder for reviewers and runtime policy to constrain what the skill is permitted to access over the network.
- Content
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 98% confidence
- Finding
The skill explicitly promotes bypassing bot protection and Cloudflare Turnstile without any warning about legal, contractual, detection, or account-ban consequences. In context, this is more dangerous because the core purpose of the skill is evasive scraping, which can facilitate unauthorized access patterns and expose operators to compliance and abuse risks.
- Content
Natural-Language Policy Violations
Medium
- Category
- Not specified by scanner
- Confidence
- 95% confidence
- Finding
This code emits all user-facing status and result messages in Russian, including the main progress, error, and summary output. The file does not offer a language selection mechanism or explain that the skill is intentionally Russian-only, which violates the policy against forcing a specific language without user opt-in.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 54% confidence
- Finding
The usage examples and target service context are entirely Russian-language focused, and the skill does not state whether users may choose another language or locale. Because SQP-3 covers language/locale policy violations, this may be a concern if the skill implicitly constrains users to Russian without opt-in.
- Content
Natural-Language Policy Violations
Low
- Category
- Not specified by scanner
- Confidence
- 66% confidence
- Finding
The documentation presents the service as Yandex.Archive and gives query examples only in Russian/Cyrillic, which can imply a locale-specific expectation. Because there is no explicit statement that users may choose their preferred language or that Russian is required for a justified region-specific reason, this may conflict with the language/locale policy guidance.
- Content