Back to skill

Security audit

Metrika Analysis

Security checks for vulnerabilities and agentic risk

Overview

This is a small Yandex.Metrika analytics helper that uses provided credentials to read site metrics and does not include code, persistence, or hidden actions.

Before installing, confirm you intend to let the agent use your Yandex.Metrika token and counter ID to read analytics for the selected site. Keep the token scoped appropriately and avoid using credentials for counters you do not want analyzed.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
Findings (2)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

All user-facing instructions and examples in the skill are written in Russian, including imperative guidance such as 'Используй этот скилл', with no indication that other languages are supported or that Russian is required for a specific regional/compliance reason. This can constitute a language/locale policy violation because the skill appears to enforce a specific language without user opt-in.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

The markdown instructs the skill to check for and use METRIKA_TOKEN and COUNTER_ID to retrieve analytics data, which implies access to credentials and potentially sensitive site analytics. While the file says it does not publish data or modify counters without permission, it does not explicitly warn the user that the skill will access account-linked analytics data using stored credentials.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.