x-grok-to-obsidian

• Outcome: Review
• Latest audit: Jul 25, 2026 · 10:40 PM UTC
• Version: 0.1.1

Overview

The skill appears intended to back up Grok chats, but it captures private authenticated conversation data broadly and leaves sensitive intermediate data in browser storage without enough upfront privacy controls.

Install only if you are comfortable running a DevTools script inside your logged-in X/Grok session and exporting your private Grok history to local files. Use a trusted browser profile and machine, avoid shared devices, inspect or redact the JSON/Markdown before syncing to Obsidian or cloud storage, and clear x.com localStorage if the capture is interrupted.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• MCP Least Privilege: Underdeclared Capability, Wildcard Permission, Missing Permission Declaration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (6)

Lp3

Medium

• Category: MCP Least Privilege
• Confidence: 94% confidence
• Finding: The skill instructs the user to run a browser-network capture script, download captured data, and then convert it locally, which implies network access plus local file read/write behavior. Because these capabilities are not explicitly declared, users and security tooling cannot accurately assess the skill's access needs, increasing the chance of unintended data exposure or misuse.

Missing User Warnings

Medium

• Confidence: 86% confidence
• Finding: The README instructs users to capture Grok/X conversation data from browser network traffic and notes that checkpoints are stored in localStorage, but it does not prominently warn that this data may contain sensitive personal content, metadata, or session-adjacent artifacts. In this context, omission of privacy guidance increases the risk that users mishandle exported chat history or leave recoverable remnants on a shared machine/browser profile.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: The script persists captured Grok conversation data and metadata into localStorage as a checkpoint, which exposes sensitive chat contents to any script running in the same origin and leaves data behind longer than necessary. Although this appears intended for resumable export rather than abuse, storing private conversation history without clear user disclosure or minimization increases privacy and data exposure risk.

Missing User Warnings

Medium

• Confidence: 90% confidence
• Finding: The code monkey-patches fetch and XMLHttpRequest to intercept Grok conversation responses, capturing private conversation data transparently from live network traffic. Even if used for user-requested backup, this interception pattern is sensitive because it collects data implicitly and could be repurposed to harvest more than the user expects.

Ssd 3

High

• Confidence: 94% confidence
• Finding: The script enumerates conversations, captures full message contents and metadata, stores intermediate results, and exports them into a downloadable JSON archive. Because Grok chats may contain highly sensitive personal, business, or credential-like information, this creates a substantial confidentiality risk if run in a shared environment, if the browser is compromised, or if the exported file is mishandled.

Context Leakage

High

• Category: Data Exfiltration

Content

Export Grok conversations in two stages.

## Stage 1 — Capture conversation JSON from X/Grok

Run the browser script in Chrome DevTools Console on `https://x.com/i/grok` while logged in.

• Confidence: 91% confidence
• Finding: The skill directs the user to capture authenticated Grok/X conversation responses while logged in, which can expose private chat content and associated metadata from an active session. Even if intended for backup, this is a context-leakage risk because sensitive data from the user's account is being extracted from live browser traffic and saved to disk.

VirusTotal

VirusTotal findings are pending for this skill version.

Static analysis

No suspicious patterns detected.