Security audit

BYR CLI Skill

Security checks for vulnerabilities and agentic risk

Overview

The skill is a coherent BYR CLI wrapper, but it asks users to install and trust an unpinned external CLI that handles browser/session credentials.

Review this skill before installing. Use it only if you trust the byr-pt-cli package source, avoid pasting real cookies or tokens into visible command lines or logs, and be cautious with browser-profile import because it gives the external CLI access to sensitive session material. Choose explicit download paths and run dry-runs first.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
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

Findings (2)

T08 · Insecure Dependencies

Error

Location: SKILL.md:13
Finding: Unpinned Third-Party CLI Dependency Executes Outside the Audited Skill Package
Content: View full analysis
Remediation: View remediation

T09 · Insecure Skill Coding Practices

Warning

Location: examples.md:55
Finding: Reusable Authentication Secrets Are Passed Through Command-Line Arguments
Content: View full analysis
" --json` - `byr auth import-cookie --from-browser [--profile ] --json` ``` ### Technical Analysis The documented authentication flow instructs users or Agents to place reusable cookie values directly in the `--cookie` command-line argument. Command-line secrets can be exposed through shell history, Agent command transcripts, debug logs, telemetry, process-list inspection, crash reports, terminal recording, or error-handling output. The affected formats include `uid` and `pass`, as well as `session_id`, `auth_token`, and an optional `refresh_token`. These values are authentication material rather than low-sensitivity configuration. A refresh token may remain useful after a short-lived access token or session expires. Live verification and authenticated operations necessarily involve communicating authentication state to the intended BYR service. That network use is consistent with the declared functionality. However, the reviewed documentation does not identify expected network destinations, transport guarantees, credential retention behavior, or redaction requirements. Because processing is delegated to the external `byr` binary, the project files alone cannot verify where the binary sends or stores those credentials. ### Attack Path 1. A user replaces the example placeholders with real BYR cookie or token ...[truncated 1479 chars]
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 (2)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The authentication examples normalize passing raw cookies and importing browser session data directly on the command line, which can expose secrets through shell history, process listings, logs, screenshots, and copied documentation. In a tool handling authenticated tracker access, these credentials may enable account takeover or unauthorized session reuse if mishandled.
Content: No source excerpt is available for this finding.

Missing User Warnings

Low

Category: Not specified by scanner
Confidence: 82% confidence
Finding: This markdown file documents a command that writes output to ./1001.torrent, which affects user data on disk. The example is presented without any accompanying warning or note that it will create or overwrite a local file, so users may not realize it changes the filesystem.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.