Evoagentx

• Outcome: Pass
• Latest audit: Sep 10, 2026 · 10:24 PM UTC
• Version: 1.0.1

Overview

This is a small, disclosed AI-framework integration skill with ordinary dependency and API-key risks but no evidence of hidden, destructive, or deceptive behavior.

Before installing, treat provider API keys as secrets, avoid hardcoding or sharing them, and assume workflow goals/prompts may be sent to the selected model provider. Consider installing evoagentx in an isolated environment and reviewing the package version because the skill does not pin a specific release or include the referenced PowerShell helper script.

A.I.G

Vulnerability Patterns

• Insecure Dependencies: Introduces malicious components through unsafe dependency sources
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally

Findings (1)

T08 · Insecure Dependencies

Warning

• Location: SKILL.md:5

Finding

Unpinned Third-Party Python Dependency

Content

View full analysis

Vulnerability Details

File Location: SKILL.md:5 and SKILL.md:29-34
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: Medium

Vulnerable Code

yaml

metadata: {"openclaw": {"emoji": "🧬", "category": "ai", "requires": {"bins": ["python3.12"], "pip": ["evoagentx"], "python_path": "C:\\Users\\z\\AppData\\Local\\Programs\\Python\\Python312\\python.exe"}, "homepage": "https://github.com/EvoAgentX/EvoAgentX"}}

powershell

# Check status first
.\evoagentx.ps1 -Action status

# Install (if needed)
.\evoagentx.ps1 -Action install

Technical Analysis

The skill declares the evoagentx package without an exact version constraint, dependency lock file, or artifact integrity hash. Consequently, installation may resolve to a different package version over time. The project also contains no vendored package code with which to verify the installed artifact.

The upstream homepage does not cryptographically bind the package retrieved by the Python package manager to the reviewed source repository. Python packages and their transitive dependencies may execute package-controlled build or installation logic. Therefore, compromise of the package distribution channel, a future malicious release, or compromise of a transitive dependency could result in code execution during installation or subsequent use.

The referenced evoagentx.ps1 script is absent from the audited project, so its package source, installation flags, and validation behavior cannot be verified.

Attack Path

1. A user activates the skill or follows the documented installation command.
2. The installation mechanism resolves evoagentx without an exact version or required hash.
3. The package manager downloads the version currently offered by the configured package index, together with applicable transitive dependencies.
4. If a resolved artifact or dependency has been compromised, package-controlled i ...[truncated 927 chars]

Remediation

View remediation

Remediation Suggestions

1. Pin evoagentx to a specifically reviewed release, for example with an exact == version constraint.
2. Generate and commit a lock file covering all transitive dependencies.
3. Require cryptographic hashes for every downloaded artifact, such as through pip's --require-hashes mode and a hash-locked requirements file.
4. Configure installation to use an explicitly trusted package index and reject unexpected fallback indexes.
5. Review the selected package release and its dependency tree before updating the pinned version.
6. Include the referenced evoagentx.ps1 script in the project so its package source, command construction, integrity checks, and error handling can be audited.
7. Avoid automatic dependency installation where practical. Perform installation in an isolated virtual environment with least-privilege permissions.
8. Keep provider API keys out of the installation process and expose them only to the runtime process that requires them.

SkillSpector

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 91% confidence

Finding

The markdown describes checking installation and API keys, and later instructs users to set an API key, but it does not include any warning about treating the key as sensitive, avoiding sharing it, or the privacy implications of transmitting prompts to third-party model providers. For a skill that interacts with external AI services and credentials, the description should disclose these risks to users.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.