T01 · Skill Instruction Hijacking
- Location
SKILL.md:119- Finding
Mandatory Remote-Triggered Instruction and Task Hijacking
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a real AI and deployment gateway, but it needs review because it can update and replace itself from a remote download, persist API keys, upload project files, and open server-provided URLs through unsafe shell commands.
Install only if you trust the SkillBoss service and publisher with local agent behavior, API credits, deployment source, and commerce workflows. Prefer manual updates, inspect any files before deployment, keep secrets out of project build folders and .env files that could be uploaded, and use least-privilege or disposable API keys where possible.
SKILL.md:119Mandatory Remote-Triggered Instruction and Task Hijacking
scripts/api-hub.js:764Automatic Retrieval and Installation of Unverified Remote Skill Packages
scripts/serve-build.js:438Worker Deployment Collects and Uploads Plaintext .env Secrets
scripts/stripe-connect.js:108Shell Command Injection Through Server-Provided Stripe Onboarding URL
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The file documents reading/writing credentials, auto-provisioning trial API keys, performing update checks, and persisting secrets in multiple local locations, none of which are clearly foregrounded in the high-level description. This expands the skill's trust boundary to local secrets and environment metadata, making misuse or unexpected exfiltration more dangerous than a pure API gateway skill.
The skill documents storing API keys in plaintext-accessible locations such as ~/.config, shell profiles, and local config.json. In an agent environment, these locations are commonly readable by tools and scripts, so broad secret discovery guidance materially increases the risk of credential exposure or misuse.
| Location | Path |
|----------|------|
| Global credentials | `~/.config/skillboss/credentials.json` |
| Shell profile | `SKILLBOSS_API_KEY` in `~/.zshrc` or `~/.bashrc` |
| Skill config | `config.json` in the skill directory |
The credential resolution order explicitly instructs the agent where to search for API keys, which facilitates secret harvesting by any over-privileged workflow or compromised companion script. Combining this with broad invocation rules and update behavior increases the blast radius if the skill or its scripts are abused.
| Shell profile | `SKILLBOSS_API_KEY` in `~/.zshrc` or `~/.bashrc` |
| Skill config | `config.json` in the skill directory |
**Resolution order:** `SKILLBOSS_API_KEY` env var > `~/.config/skillboss/credentials.json` > `config.json`
### When balance is low
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
Referenced artifact was not completely inspected
node ./scripts/api-hub.js version
The documentation instructs readers to source an API key from local credential storage and copy it into an application environment, which can encourage unsafe secret handling and propagation of privileged credentials into broader build/runtime contexts. In this skill context, the same key authorizes billable external API use, so exposure could enable unauthorized usage, credit theft, or abuse of integrated services.
## Setup Steps
1. Run `./scripts/skillboss auth trial` or `./scripts/skillboss auth login` to get an API key
2. The key is auto-saved to `~/.config/skillboss/credentials.json` and exported as `SKILLBOSS_API_KEY`
3. For app code, add `SKILLBOSS_API_KEY` to your project's `.env` file
4. Use the code patterns above, adjusting for your specific model
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
pnpm i mapbox-gl @turf/turf @types/mapbox-gl
The user needs to create a free Mapbox account and create an access token by visiting https://console.mapbox.com/account/access-tokens/.
The mapbox token needs to be added to the `.env` file:
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
The mapbox token needs to be added to the .env file:
REMOTION_MAPBOX_TOKEN==pk.your-mapbox-access-token
The style string contains an unusual invisible character before mapbox://styles/..., which can mislead readers and cause copy/paste discrepancies or hard-to-diagnose runtime errors. Hidden or non-printing characters in code examples are risky because they obscure the actual content and can be abused to conceal altered values or instructions.
center: [6.5615, 46.0598],
pitch: 65,
bearing: 0,
style: 'mapbox://styles/mapbox/standard',
interactive: false,
fadeDuration: 0,
});
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
if [ -d "$dest/skillboss" ]; then
if [ "$AUTO_OVERWRITE" = true ]; then
rm -rf "$dest/skillboss"
else
echo -e "${YELLOW}! $name: skillboss already exists${NC}"
read -p " Overwrite? [y/N]: " confirm
Detected: suspicious.dangerous_exec, suspicious.env_credential_access