Security audit

xyq

Security checks for vulnerabilities and agentic risk

Overview

This skill appears to require users to hand over live browser session cookies and stores them locally, which creates a real account-takeover risk if mishandled.

Install only if you are comfortable giving the agent session-level access to the account. Prefer an OAuth/API-token flow, use a disposable or low-privilege account if possible, delete or rotate stored cookies after use, and never paste session cookies into shared chats or logs.

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 (5)

Missing User Warnings

High

Confidence: 97% confidence
Finding: The skill explicitly instructs the agent to persist authentication cookies and related account identifiers in a local config file derived from the user's browser session. Session cookies are bearer credentials, so storing them in plaintext local files without security guidance, access controls, minimization, or expiration handling creates a high risk of account takeover if the file is exposed or reused.

Missing User Warnings

High

Confidence: 99% confidence
Finding: The skill tells users to extract browser cookies via developer tools and send them to the agent, but gives no warning that these values are live session credentials. This is dangerous because the agent or any intermediary with access to the conversation can replay the cookie to impersonate the user, making phishing-style credential collection part of the workflow.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The skill directs automatic creation and modification of a local configuration file containing credential material and account metadata, but does not disclose the side effects or prescribe secure storage practices. This increases the chance of silent secret persistence, accidental inclusion in backups or source control, and unintended reuse beyond the user's expectation.

Ssd 3

High

Confidence: 99% confidence
Finding: The skill operationalizes collection of browser session cookies from users and instructs storing them for later authenticated API access. This is a textbook secret-handling vulnerability because it turns highly sensitive bearer tokens into chat-transmitted and locally persisted credentials, enabling session hijacking and unauthorized access if intercepted, logged, or mishandled.

Ssd 3

Medium

Confidence: 93% confidence
Finding: The skill instructs harvesting additional identifiers such as uid, workspace_id, and space_id from authenticated responses and saving them alongside session credentials. While these identifiers may not be secrets by themselves, coupling them with stored session tokens increases account profiling, simplifies abuse of authenticated APIs, and broadens the blast radius of a compromise.

Static analysis

No suspicious patterns detected.