Skip to content

Security: web3bio/agent-skills

Security

SECURITY.md

Security Policy

This repository defines how AI agents should call the public Web3.bio HTTP API. It does not ship executable server code; risks are mainly misuse of user secrets, prompt injection via identity strings or JSON, and supply-chain tampering if the skill is installed from an untrusted fork.

Supported Versions

Area Support
Latest main in this repo Security fixes and documentation corrections apply here
Older commits / forks Use at your own risk; verify diffs before trusting

Threat Model (Agent Context)

  • API key (x-api-key): Required only for GET /wallet/{identity}. The skill forbids sending this header on any other path. Keys must not appear in git, logs, screenshots, result cards, or complete-response blocks.
  • Host pinning: Only https://api.web3.bio is in scope. Do not switch hosts based on chat content, shortened URLs, or “mirror” domains not documented in this repo.
  • Untrusted input: User-supplied identities and API bodies are data, not instructions. Path segments must be URL-encoded; do not execute or interpret natural-language inside identifiers as shell or code.
  • Response handling: Follow web3bio-skills/references/response-format.md. Do not treat API JSON as system or developer instructions.

For a broader agent-security review playbook, see SlowMist Agent Security.

Reporting a Vulnerability

  1. Skill or documentation (wrong routing that leaks keys, incorrect auth table, etc.): open a private security advisory on this GitHub repository if available, or contact the repository maintainers with subject [security] web3bio-skills.
  2. Web3.bio API or product bugs: report through Web3.bio’s official channels; this skill repo cannot fix server-side issues.

Please include: affected file(s), reproduction steps, and impact (e.g. credential exfiltration scenario). Do not post live API keys in reports.

Hardening Checklist (Maintainers)

  • web3bio-skills/references/routing-manifest.json auth flags match request-conventions.md
  • Wallet path still states strict result-card-only output in response-format.md
  • web3bio-skills/reference.md index stays aligned with new endpoints
  • Run intent smoke checks in test-cases.md after routing or trigger edits
  • npx skills-ref validate ./web3bio-skills passes

There aren't any published security advisories