Security audit

Gougoubi Submit Real Results

Security checks for vulnerabilities and agentic risk

Overview

This skill is purpose-built for blockchain result submission, but it under-discloses irreversible transaction risk and points agents at unbundled relative scripts for high-impact actions.

Review carefully before installing. Only use it in a controlled repository where the referenced scripts are known, reviewed, and pinned, and require a manual confirmation of chain, signer, proposal, condition results, calldata, fees, and dry-run output before any real submission.

A.I.G

Vulnerability Patterns

Tool Hijacking and SpoofingModifies or replaces tools so legitimate-looking calls execute attacker logic
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)

T07 · Tool Hijacking and Spoofing

Error

Location: SKILL.md:91
Finding: Unbundled Relative Script Entry Points Can Execute Unverified Local Code
Content: View full analysis
--result yes --dry-run` - `node scripts/pbft-submit-results-from-skills-once.mjs --help` - `node scripts/pbft-submit-results-from-skills-once.mjs ` - Specialized scripts also support `--help` for their fixed proposal mappings. ``` `INSTALL.md:21-29`: ```markdown ## Post-install check If the local project scripts are available, verify the public entrypoints first: ```bash node scripts/pbft-submit-results-from-skills-once.mjs --help node scripts/pbft-submit-all-condition-results.mjs --help node scripts/pbft-submit-all-condition-results.mjs --result yes --dry-run ``` Restart the agent runtime after installation. ``` `README.md:18-26`: ```markdown Script entry: - `scripts/pbft-submit-results-from-skills-once.mjs` - `scripts/pbft-submit-all-condition-results.mjs` - `node scripts/pbft-submit-results-from-skills-once.mjs --help` - `node scripts/pbft-submit-results-from-skills-once.mjs ` - `node scripts/pbft-submit-all-condition-results.mjs --result yes --dry-run` ``` ### Technical Analysis The aud ...[truncated 3027 chars]
Remediation: View remediation

SkillSpector

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)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The skill explicitly performs on-chain result submissions, yet it does not clearly warn users that invoking it may create irreversible blockchain transactions with settlement consequences. In a blockchain governance/settlement context, insufficient disclosure can lead to accidental execution, unintended votes, and irreversible state changes if the agent proceeds without an explicit high-friction confirmation step.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The description is broadly scoped ('Use when users want ... outcomes submitted ... with resolved-only, all, and force modes') and does not define narrow activation conditions or safety gates. In an automation skill that can submit settlement results for prediction-market conditions, vague triggering increases the chance the agent invokes it in the wrong context, including premature or force-mode submissions based on incomplete evidence.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.