cliamp-terminal-music-player
Fail
Audited by Gen Agent Trust Hub on May 17, 2026
Risk Level: CRITICALREMOTE_CODE_EXECUTIONCOMMAND_EXECUTIONEXTERNAL_DOWNLOADS
Full Analysis
- [REMOTE_CODE_EXECUTION]: The installation section provides a command to pipe a remote script to the shell:
curl -fsSL https://raw.githubusercontent.com/bjarneo/cliamp/HEAD/install.sh | sh. This pattern is highly insecure as it executes arbitrary code from a remote source with the user's privileges without any integrity checks. The source repositorygithub.com/bjarneois an unverified third-party account. - [COMMAND_EXECUTION]: The skill provides instructions for building and running code from unverified external repositories. Compiling from source using
git clone https://github.com/bjarneo/cliamp.gitandmake installexecutes potentially untrusted build instructions. Installation of community plugins viagit clone https://github.com/bjarneo/cliamp-plugin-soap-bubbles.gitintroduces unverified dynamic code into the application environment. - [EXTERNAL_DOWNLOADS]: The skill directs users to fetch and run software from unverified third-party GitHub repositories for both the main application and its extensions.
- [REMOTE_CODE_EXECUTION]: The integrated Lua plugin system allows for dynamic execution of local scripts which can perform network operations via
http_get, creating a surface for indirect prompt injection and data exfiltration if processing untrusted audio metadata. 1. Ingestion points: Track metadata (title, artist, album) processed inon_track_changeinplugin.lua. 2. Boundary markers: Absent. 3. Capability inventory: Lua plugins can perform network requests (http_get) and log messages. 4. Sanitization: Absent.
Recommendations
- HIGH: Downloads and executes remote code from: https://raw.githubusercontent.com/bjarneo/cliamp/HEAD/install.sh - DO NOT USE without thorough review
- AI detected serious security threats
Audit Metadata