T08 · Insecure Dependencies
- Location
scripts/docker-compose.yml:4- Finding
Unpinned Third-Party Container Receives the API Token and Workspace Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to perform the advertised code remediation workflow, but its examples give automation and an unpinned container access to your code and Gomboc token, with commit/push remediation and weak safeguards.
Install only if you trust Gomboc and are comfortable sending repository context to its service. Avoid the Docker MCP mode unless you pin the image digest, bind it to 127.0.0.1, and restrict workspace/token scope. Do not use --commit/--push or autonomous remediation on important branches without review and branch protection, and avoid printing or storing the PAT in shell profiles or logs.
scripts/docker-compose.yml:4Unpinned Third-Party Container Receives the API Token and Workspace Access
scripts/docker-compose.yml:7MCP Service Is Published on All Host Interfaces Without Documented Request Authentication
scripts/cli-wrapper.py:244Token Status Command Reveals a Reusable Prefix of the Secret
references/setup.md:23Documentation Encourages Plaintext PAT Storage and Full Token Printing
references/github-action.md:23GitHub Actions Examples Use Mutable Tags in Secret-Bearing Write-Capable Workflows
Credentials or environment variables flow to a network sink. This is a high-confidence indicator of credential exfiltration.
method="POST"
)
with urllib.request.urlopen(req, timeout=30) as response:
result = json.loads(response.read())
if "errors" in result:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Python 3.7+
- Gomboc account (free at https://app.gomboc.ai)
- Personal Access Token from Gomboc
## 1. Get a Token
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Python 3.7+
- Gomboc account (free at https://app.gomboc.ai)
- Personal Access Token from Gomboc
## 1. Get a Token
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
1. Sign up at https://app.gomboc.ai (Community Edition is free)
2. Go to Settings → API Tokens
3. Generate a new Personal Access Token
4. Copy the token (starts with `gpt_`)
## 2. Set Environment Variable
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
1. Sign up at https://app.gomboc.ai (Community Edition is free)
2. Go to Settings → API Tokens
3. Generate a new Personal Access Token
4. Copy the token (starts with `gpt_`)
## 2. Set Environment Variable
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
1. Sign up at https://app.gomboc.ai (Community Edition is free)
2. Go to Settings → API Tokens
3. Generate a new Personal Access Token
4. Copy the token (starts with `gpt_`)
## 2. Set Environment Variable
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
1. Sign up at https://app.gomboc.ai (Community Edition is free)
2. Go to Settings → API Tokens
3. Generate a new Personal Access Token
4. Copy the token (starts with `gpt_`)
## 2. Set Environment Variable
YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
oc account (free at https://app.gomboc.ai)
gpt_)export GOMBOC_PAT="gpt_your_token_here"
Or add to your shell profile:
echo 'export GOMBOC_PAT="gpt_your_token_here"' >> ~/.bashrc
source ~/.bashrc
bash scripts/verify-setup.sh
Should output:
✅ GOMBOC_PAT is set
✅ Python 3 found: Python 3.7+
✅ CLI wrapper found
✅ API connection successful
✅ Setup verification complete!
python scripts/cli-wrapper.py scan --path ./src
export GOMBOC_PAT="your_token"
This markdown file states that the CLI makes real API calls, manages authentication, and can apply fixes directly to the codebase, but it does not warn users about code modification, external data transmission, or authentication/privacy implications. For markdown files, SQP-2 applies when descriptions omit warnings about behaviors affecting user data, privacy, or system integrity.
The README promotes scanning and automatic fix generation but does not clearly warn users that running the tool can modify code or working-tree contents. In an agent skill context, that omission is more dangerous because autonomous systems may invoke remediation commands without explicit human confirmation, increasing the risk of unintended file changes.
The skill explicitly promotes direct remediation with commit and push behavior, but does not provide clear cautions about destructive changes, review requirements, repository safety, or rollback expectations. In an agent context, encouraging autonomous modification of code and infrastructure without guardrails increases the risk of unintended commits, broken deployments, or unsafe changes being applied automatically.
The documented gomboc config --show-token command reveals a sensitive credential, yet the skill provides no warning about secret exposure in terminals, logs, shell history, screenshots, or agent transcripts. In agent and CI/CD settings, such a command materially increases the chance of inadvertent credential disclosure.
The documented workflow includes an auto-remediation step that commits and pushes code changes directly from CI using --commit --push, but it does not prominently warn users that enabling this behavior grants automation the ability to modify repository contents. This is risky because users may copy the example as-is and unintentionally allow automated changes on push or PR events, increasing the chance of unsafe, incorrect, or policy-violating code being written back to the repository without adequate human review.
The guide instructs users to configure a Personal Access Token and invoke scan/fix workflows against an MCP service without warning that source code, metadata, or remediation context may be transmitted to the server or upstream service. In a code-remediation setting, this can lead to unintentional disclosure of proprietary or sensitive repository contents.
The documented commands include fix, remediate, and commit:true, which can modify repository contents and create commits, but the guide does not warn users about these side effects. In an agent-executed context, omission of this warning increases the risk of unintended code changes being applied automatically, especially if users assume commands are read-only.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl http://localhost:3100/health
The setup guide instructs users to place a personal access token directly into an exported environment variable and persist it in ~/.bashrc, but it does not warn about credential sensitivity, local file exposure, shell/profile persistence, or safer secret-handling alternatives. While common in developer docs, this increases the chance of accidental token leakage through shared accounts, backups, dotfile sync, screenshots, or improper terminal/history practices.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
from pathlib import Path
GOMBOC_PAT = os.getenv("GOMBOC_PAT")
GOMBOC_API_URL = "https://api.app.gomboc.ai/graphql"
def call_gomboc_api(query, variables=None):
"""Call Gomboc GraphQL API."""
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
from pathlib import Path
GOMBOC_PAT = os.getenv("GOMBOC_PAT")
GOMBOC_API_URL = "https://api.app.gomboc.ai/graphql"
def call_gomboc_api(query, variables=None):
"""Call Gomboc GraphQL API."""
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
from pathlib import Path
GOMBOC_PAT = os.getenv("GOMBOC_PAT")
GOMBOC_API_URL = "https://api.app.gomboc.ai/graphql"
def call_gomboc_api(query, variables=None):
"""Call Gomboc GraphQL API."""
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
from pathlib import Path
GOMBOC_PAT = os.getenv("GOMBOC_PAT")
GOMBOC_API_URL = "https://api.app.gomboc.ai/graphql"
def call_gomboc_api(query, variables=None):
"""Call Gomboc GraphQL API."""
The code warns that '--apply will modify your code' and the CLI help defines '--apply' as 'Apply fixes', which communicates that invoking this flag changes local code. However, the fix() function never uses args.apply beyond printing the warning and only calls generateFixes then prints results, so the documented behavior contradicts the actual implementation.
The remediate command can trigger remote code modifications and optionally commit and push them based only on CLI flags, with no explicit confirmation or dry-run step. In an agent or automation context, this increases the chance of unintended destructive changes being applied to a repository and propagated to remotes without sufficient operator awareness.
The top-level documentation presents this as a 'CLI Tool' for 'scanning and fixing code issues' and a 'fully functional wrapper around the Gomboc API'. In practice, every substantive operation sends paths and commands to the external GraphQL service, so the local code does not itself scan or fix code; it is strictly a network client wrapper.