Back to skill

Security audit

LYGO Champion: scenar paradox

Security checks for vulnerabilities and agentic risk

Overview

This is a small persona-helper skill with disclosed local reference files and no automatic harmful actions, though its manual successor install command should be reviewed before use.

Installing the skill itself appears low risk, but treat the npx clawhub@latest successor command as remote code execution: pin or review the installer and successor package first if you operate in a sensitive environment. Do not rely on the bundled self-check as cryptographic proof of authenticity; verify the persona pack hash independently if integrity matters.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T08 · Insecure Dependencies

Error
Location
SKILL.md:8
Finding

Unpinned Remote Package Execution Through Mutable Latest Release

Content
View full analysis
**Consolidated (Δ9 v2):** New installs → `lygo-champion-council`. This slug is legacy retention only. > `npx clawhub@latest install deepseekoracle/lygo-champion-council` ``` ### Technical Analysis The documented installation command uses `npx` to download and execute the mutable `latest` release of the `clawhub` package. Neither the executable package nor the successor Skill is pinned to a reviewed immutable version or cryptographic digest. Because the `latest` tag can be reassigned after this project has been audited, the code executed by users may differ from the code that was originally reviewed. Compromise of the package registry, publisher account, package maintainership, or successor Skill could turn the installation instruction into a supply-chain execution path. The command is presented as a manual installation instruction rather than being automatically invoked by the bundled Python scripts. Exploitation therefore requires a user or agent to follow the documented command. ### Attack Path 1. An attacker compromises the `clawhub` package, its publisher account, its dependency chain, or the referenced successor Skill. 2. The attacker publishes a malicious release and assigns it to the mutable `latest` tag, or changes the content subsequently retrieved by the installer. 3. A user follows the installation command in `SKILL.md`. 4. `npx` retrieves and executes the attacker-controlled package. 5. The malicious package runs with the operating-system privileges and environment access of the invoking user. 6. Depending on those privileges, it could access project files, environment variables, user-readable credentials, or install additional malicious content. ### Impact Assessment Successful exploitation could result in arbitrary code execution with the priv ...[truncated 444 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/self_check.py:23
Finding

Self-Check Does Not Cryptographically Verify Persona Pack Integrity

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (9)

Tp4

High
Category
MCP Tool Poisoning
Confidence
95% confidence
Finding

The deprecated/redirect-like description does not disclose that the skill reads a local file and outputs a hash value from 'references/canon.json'. Hidden operational behavior, even if low-risk by itself, undermines review and consent and may expose internal metadata or create a misleading security posture for a supposedly passive alias.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The deprecated/redirect-like description does not disclose that the skill reads a local file and outputs a hash value from 'references/canon.json'. Hidden operational behavior, even if low-risk by itself, undermines review and consent and may expose internal metadata or create a misleading security posture for a supposedly passive alias.

Content

No source excerpt is available for this finding.

Ae4

Medium
Category
analysis-evasion
Confidence
80% confidence
Finding

Suspicious Unicode normalization or mixed-script content

Content

No source excerpt is available for this finding.

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
74% confidence
Finding

The skill references reading local files such as 'references/canon.json' but does not declare an explicit tool scope or allowed tools. This can create a trust gap where consumers believe the skill is only a deprecated persona/redirect while it still relies on filesystem access, increasing the chance of over-broad execution or unnoticed data access in permissive runtimes.

Content

No source excerpt is available for this finding.

Rp1

Medium
Category
MCP Rug Pull
Confidence
88% confidence
Finding

The install command uses 'npx clawhub@latest', which pulls an unpinned, mutable version at execution time. If the upstream package is compromised or behavior changes unexpectedly, users following the skill's instructions could execute attacker-controlled or unreviewed code.

Content

No source excerpt is available for this finding.

Ae4

Medium
Category
analysis-evasion
Confidence
93% confidence
Finding

The JSON contains mixed-script and visually confusable Unicode characters such as Greek letters in identifiers and display strings (for example, "ΣCENΔR"). Even though this appears to be branding or canon metadata rather than executable code, mixed-script text can enable spoofing, operator confusion, and mismatches between displayed and compared values if these strings are later used in lookups, access control, or filename generation.

Content

No source excerpt is available for this finding.

Ae4

Medium
Category
analysis-evasion
Confidence
80% confidence
Finding

Suspicious Unicode normalization or mixed-script content

Content

No source excerpt is available for this finding.

Ae4

Medium
Category
analysis-evasion
Confidence
80% confidence
Finding

Suspicious Unicode normalization or mixed-script content

Content

No source excerpt is available for this finding.

Ae4

Medium
Category
analysis-evasion
Confidence
80% confidence
Finding

Suspicious Unicode normalization or mixed-script content

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.