Security audit

ableton-live

Security checks for vulnerabilities and agentic risk

Overview

This skill is a clearly scoped Ableton Live helper that only reads a local bridge token and performs user-directed Live edits through the Loophole Bridge.

Before installing, understand that this gives an agent a path to your local Ableton bridge and can modify Live sets when you approve recipes. Treat the bridge token as sensitive local configuration, review any generated MCP config before applying it, and confirm mutation counts before write operations.

SkillSpector

Vulnerability Patterns

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
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (7)

Whitespace Padding

Medium

Category: Prompt Injection
Content: ## The five checks | # | Check | How | FIX line on failure | | --- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | 1 | A supported current Live beta is running | Confirm an Ableton Live process is up; check 4 is the stronger bridge signal | "Open the Live beta build used to package and test this extension." | | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." |
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Whitespace Padding

Medium

Category: Prompt Injection
Content: ## The five checks | # | Check | How | FIX line on failure | | --- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | 1 | A supported current Live beta is running | Confirm an Ableton Live process is up; check 4 is the stronger bridge signal | "Open the Live beta build used to package and test this extension." | | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." |
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Whitespace Padding

Medium

Category: Prompt Injection
Content: | # | Check | How | FIX line on failure | | --- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | 1 | A supported current Live beta is running | Confirm an Ableton Live process is up; check 4 is the stronger bridge signal | "Open the Live beta build used to package and test this extension." | | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." | | 3 | Node >= 24.14.1 | run `node --version` and compare | "Update Node to >= 24.14.1." | | 4 | Bridge port reachable | read `port` from `bridge.json`, then `GET http://127.0.0.1:<port>/mcp` with header `Authorization: Bearer <token>`; expect a valid MCP response, not a connection refusal | "Live is running but the bridge did not answer on <port>. Restart L ...[truncated 24 chars]
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Whitespace Padding

Medium

Category: Prompt Injection
Content: | # | Check | How | FIX line on failure | | --- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | 1 | A supported current Live beta is running | Confirm an Ableton Live process is up; check 4 is the stronger bridge signal | "Open the Live beta build used to package and test this extension." | | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." | | 3 | Node >= 24.14.1 | run `node --version` and compare | "Update Node to >= 24.14.1." | | 4 | Bridge port reachable | read `port` from `bridge.json`, then `GET http://127.0.0.1:<port>/mcp` with header `Authorization: Bearer <token>`; expect a valid MCP response, not a connection refusal | "Live is running but the bridge did not answer on <port>. Restart L ...[truncated 25 chars]
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Whitespace Padding

Medium

Category: Prompt Injection
Content: | --- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | 1 | A supported current Live beta is running | Confirm an Ableton Live process is up; check 4 is the stronger bridge signal | "Open the Live beta build used to package and test this extension." | | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." | | 3 | Node >= 24.14.1 | run `node --version` and compare | "Update Node to >= 24.14.1." | | 4 | Bridge port reachable | read `port` from `bridge.json`, then `GET http://127.0.0.1:<port>/mcp` with header `Authorization: Bearer <token>`; expect a valid MCP response, not a connection refusal | "Live is running but the bridge did not answer on <port>. Restart Live, and check that no other app holds the port." | | 5 | Token present | `bridge.json` contains a non-empty `token` | "No token in bridge.json. Reinstall or restart the extension to reg ...[truncated 24 chars]
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Whitespace Padding

Medium

Category: Prompt Injection
Content: | --- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | 1 | A supported current Live beta is running | Confirm an Ableton Live process is up; check 4 is the stronger bridge signal | "Open the Live beta build used to package and test this extension." | | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." | | 3 | Node >= 24.14.1 | run `node --version` and compare | "Update Node to >= 24.14.1." | | 4 | Bridge port reachable | read `port` from `bridge.json`, then `GET http://127.0.0.1:<port>/mcp` with header `Authorization: Bearer <token>`; expect a valid MCP response, not a connection refusal | "Live is running but the bridge did not answer on <port>. Restart Live, and check that no other app holds the port." | | 5 | Token present | `bridge.json` contains a non-empty `token` | "No token in bridge.json. Reinstall or restart the extension to reg ...[truncated 24 chars]
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Whitespace Padding

Medium

Category: Prompt Injection
Content: | 2 | The extension is installed and active | `bridge.json` exists in the extension `storageDirectory` | "Install the Loophole extension `.ablx` in Live, Settings, Extensions, then restart Live." | | 3 | Node >= 24.14.1 | run `node --version` and compare | "Update Node to >= 24.14.1." | | 4 | Bridge port reachable | read `port` from `bridge.json`, then `GET http://127.0.0.1:<port>/mcp` with header `Authorization: Bearer <token>`; expect a valid MCP response, not a connection refusal | "Live is running but the bridge did not answer on <port>. Restart Live, and check that no other app holds the port." | | 5 | Token present | `bridge.json` contains a non-empty `token` | "No token in bridge.json. Reinstall or restart the extension to regenerate it." | Notes on the checks:
Confidence: 70% confidence
Finding: Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.

Static analysis

No suspicious patterns detected.