ClawHub
Back to skill

Security audit

Bitwarden Bw

Security checks for vulnerabilities and agentic risk

Overview

The skill is a simple Bitwarden CLI helper, but it tells users to persist a vault session secret in a shell startup file.

Review carefully before installing. If you use it, do not save BW_SESSION in ~/.zshrc or any shell profile; unlock Bitwarden only for the current shell, unset BW_SESSION when finished, and lock the vault after use.

A.I.G

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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)

T09 · Insecure Skill Coding Practices

Error
Location
SKILL.md:14
Finding

Bitwarden Session Secret Persisted in a Shell Startup File

Content
View full analysis
Remediation
View remediation

SkillSpector

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

High
Category
Not specified by scanner
Confidence
98% confidence
Finding

The skill explicitly instructs users to keep the Bitwarden session token in the BW_SESSION environment variable persisted in ~/.zshrc, which stores a reusable secret in a shell startup file. Shell RC files are long-lived, commonly readable by local processes or exposed through backups, dotfile sync, screenshots, support bundles, or accidental sharing, so compromise of that token can allow unauthorized access to the user's vault for the life of the session.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.