Back to skill

Security audit

Auto Data Analyzer

Security checks for vulnerabilities and agentic risk

Overview

This skill is a straightforward data-analysis helper, with ordinary cautions around installing Python packages and saving generated report files.

Install this only in a virtual environment and avoid running package installation as administrator. Be mindful that reports, charts, and CSV summaries may persist sensitive dataset contents on disk, so choose output locations deliberately.

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:47
Finding

Unpinned Third-Party Python Dependencies

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, line 47
Vulnerability Type: Supply-chain risk from unpinned dependencies
Risk Level: Medium

Complete Code Snippet

bash
pip install pandas numpy matplotlib seaborn scikit-learn

Technical Analysis

The installation command retrieves five third-party packages without pinning exact versions or verifying package hashes. Consequently, installation results can change over time and depend on the configured Python package index. The command also provides no mechanism to ensure that downloaded artifacts are the versions reviewed by the project author.

If an upstream package, transitive dependency, release account, or configured package index is compromised, following this instruction could install attacker-controlled code. Python packages may execute build or installation logic, and malicious code may also run when the installed package is imported.

The audit did not identify dependency confusion or typosquatting in the listed package names; the finding concerns the absence of version and integrity controls.

Attack Path

  1. An attacker compromises a listed package, one of its transitive dependencies, a maintainer account, or a package index configured by the user.
  2. The attacker publishes a malicious artifact under a version accepted by the unpinned installation command.
  3. A user follows the documented command.
  4. pip resolves and downloads the attacker-controlled artifact because no exact version or trusted hash is required.
  5. Malicious code executes during package installation, build processing, or subsequent import and use.

Impact Assessment

Successful exploitation could execute code with the privileges of the user running pip or the analysis tool. Depending on those privileges, the attacker could access or modify files available to that account, steal data processed by the analyzer, alter generated reports, access environment-held credentials, or install additional p ...[truncated 165 chars]

Remediation
View remediation

Remediation Suggestions

  1. Create a reviewed dependency lock file containing exact versions and cryptographic hashes.
  2. Install dependencies with hash enforcement, for example:
    bash
    python -m pip install --require-hashes -r requirements.txt
    
  3. Generate and review the lock file through a reproducible dependency-management process.
  4. Regularly scan direct and transitive dependencies for known vulnerabilities and update them through controlled review.
  5. Use a virtual environment and avoid running package installation with administrator or root privileges.
  6. Configure pip to use a trusted package index and disallow unexpected additional indexes.
  7. Include the referenced implementation files (analyzer.py and main.py) so the documented behavior and actual dependency usage can be audited.
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (2)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The skill description is broad enough to match many routine requests involving data analysis, reports, or visualization, which can cause the agent to invoke this skill in situations the user did not clearly intend. Over-broad activation increases the chance of unnecessary file handling and analysis on user-provided datasets, expanding exposure to downstream risks from processing sensitive or untrusted data.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill documents report and artifact generation but does not clearly warn that it writes HTML, PNG, and CSV files to disk. Missing disclosure can lead to unexpected persistence of potentially sensitive data, accidental overwrites, or creation of output files in insecure locations when users believe the analysis is in-memory only.

Content

No source excerpt is available for this finding.