Back to skill

Security audit

Fuel CLI

Security checks for vulnerabilities and agentic risk

Overview

The skill has a coherent fuel-price lookup purpose, but it relies on an unpinned global npm CLI while also asking users to provide OAuth secrets.

Review the npm package before installing, prefer a pinned version or local install where possible, and store FUEL_FINDER_CLIENT_ID and FUEL_FINDER_CLIENT_SECRET securely outside committed files. Only set FUEL_FINDER_BASE_URL to a trusted HTTPS Fuel Finder endpoint.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:17
Finding

Unpinned Third-Party npm Package Installed Globally

Content
View full analysis
Remediation
View remediation
``` 2. Record and verify the expected package integrity digest. Use a lockfile or an equivalent reproducible dependency manifest where the installation environment supports it. 3. Prefer a project-local installation over a global installation: ```bash npm install --save-exact @shan8851/fuel-cli@ ``` Invoke it through a controlled project script or a locally resolved binary rather than adding it globally to the user's command path. 4. Publish or vendor the corresponding reviewed source code so that credential handling, outbound requests, cache permissions, command parsing, and npm lifecycle scripts can be audited. 5. Disable npm lifecycle scripts during installation when they are not required: ```bash npm install --ignore-scripts --save-exact @shan8851/fuel-cli@ ``` 6. Run the CLI with least privilege and expose credentials only to the specific process that requires them. Do not install or invoke it as an administrator unless independently justified. 7. Restrict `FUEL_FINDER_BASE_URL` to approved HTTPS endpoints in the implementation so OAuth credentials cannot be accidentally transmitted to an untrusted host. 8. Establish a dependency update process in which new package versions and their integrity values are reviewed before the pinned version is changed. ]]>
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (1)

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
82% confidence
Finding

This markdown file instructs users to export FUEL_FINDER_CLIENT_ID and FUEL_FINDER_CLIENT_SECRET or add them to .env, which involves handling credentials. While setup is clear, the documentation does not include any caution about protecting the .env file, avoiding commits, or treating these values as secrets.

Content

No source excerpt is available for this finding.