Back to skill

Security audit

muapi-platform

Security checks for vulnerabilities and agentic risk

Overview

The skill matches its MuAPI utility purpose, but its recommended setup can expose a MuAPI API key in command history and process arguments.

Before installing, prefer the interactive setup form, avoid typing the API key directly into a command, check where the muapi CLI stores credentials, and rotate any key previously entered through the documented command-line example.

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
setup.sh:8
Finding

API Key Exposed Through Shell History and Process Arguments

Content
View full analysis
Remediation
View remediation
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 (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
85% confidence
Finding

The markdown instructs users to provide and store an API key and to test it, but it does not include any user-facing warning about credential sensitivity, storage location, or the privacy/security implications of exposing or persisting the key. Under the markdown criteria for missing user warnings, credential-related behavior should be disclosed when it could affect user data or privacy.

Content

No source excerpt is available for this finding.