T03 · Remote Payload Retrieval and Execution
- Location
config/mcporter.json:4- Finding
Unpinned Remote GitHub Package Is Automatically Downloaded and Executed with Banking Credentials
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed banking integration, but it auto-runs mutable GitHub code with a sensitive banking API key.
Install only if you are comfortable giving this MCP server access to your Brighty owner API token. Prefer a pinned, reviewed commit or vetted package release, use the least-privileged revocable token available, keep payout confirmations outside the MCP server, and monitor or rotate the token if the dependency changes.
config/mcporter.json:4Unpinned Remote GitHub Package Is Automatically Downloaded and Executed with Banking Credentials
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
### 2. Get API key
Go to [Account > Business](https://business.brighty.app/account/business) and click **Create API Token**. Only the business **owner** can do this.
### 3. Configure
The skill instructs users to launch an MCP server directly from a GitHub source via npx -y github:Maay/brighty_mcp without pinning a specific commit or immutable version. This creates a supply-chain risk: the referenced code can change over time or be compromised, and because the skill handles banking actions and an API key, a malicious update could exfiltrate credentials or execute unauthorized financial operations.
No suspicious patterns detected.