Security audit

Quark

Security checks for vulnerabilities and agentic risk

Overview

This appears to be a real Quark Drive management skill, but it needs Review because it handles account cookies and powerful cloud-file actions with some unsafe or under-scoped guidance.

Install only if you are comfortable giving this skill access to your Quark Drive account. Protect QUARK_COOKIE and the saved config file like a password, avoid uploading hidden or agent directories such as ~/.hermes, review exact paths before delete/clear/download commands, and prefer short-lived password-protected shares over public or permanent links.

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access

Findings (8)

Context-Inappropriate Capability

Low

Confidence: 93% confidence
Finding: The code reads authentication material from an environment variable and persists the Quark session cookie in plaintext under the user's home directory. If the local system, account, or dotfiles are exposed, an attacker could reuse the stored cookie to access the user's cloud drive without re-authenticating.

Vague Triggers

Medium

Confidence: 88% confidence
Finding: The trigger description is broad enough to match generic file-management requests such as upload, download, or sharing, which may cause the skill to activate outside clearly intended Quark Drive contexts. Misrouting increases the chance of unintended file operations or credential use in situations where the user did not explicitly ask to interact with Quark Drive.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The skill exposes delete and clear operations but does not document mandatory confirmation, preview, or recovery expectations. In a cloud-storage context, destructive actions can lead to irreversible user data loss if triggered accidentally, misunderstood, or routed from ambiguous prompts.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The skill supports creating share links, including permanent shares, without warning that links may expose private files to unintended recipients and can remain accessible for long periods. In cloud storage, this can cause confidentiality breaches, especially if users omit passcodes or mistakenly share sensitive content.

Missing User Warnings

Medium

Confidence: 96% confidence
Finding: The documentation instructs users to store QUARK_COOKIE but does not warn that it is a sensitive authentication credential equivalent to an active session. If exposed through shell history, logs, screenshots, or shared config files, an attacker could access the user's cloud drive, files, and sharing capabilities.

Missing User Warnings

Medium

Confidence: 87% confidence
Finding: The document explicitly instructs saving high-value authentication cookies (__pus, __kps, __uid) but does not warn that these credentials can authenticate as the user and must be handled as secrets. In the context of a cloud-drive skill that supports file listing, upload, download, sharing, transfer, and deletion, cookie leakage would enable unauthorized access to the user's storage and account actions.

Missing User Warnings

Medium

Confidence: 96% confidence
Finding: Session cookies are saved to disk without any warning, consent flow, or protection mechanism. Because cookies act as bearer credentials, plaintext storage can lead to account compromise if another local process, user, backup system, or malware reads the config file.

Missing User Warnings

Medium

Confidence: 86% confidence
Finding: The download command writes server-provided content directly to any caller-supplied local path and does not warn about overwriting sensitive files or modifying local state. In an agent setting, a manipulated path could overwrite important user files, shell profiles, or application data, causing data loss or persistence opportunities.

Static analysis

No suspicious patterns detected.