Security audit

X-scraper/推文抓取工具

Security checks across malware telemetry and agentic risk

Overview

This is a disclosed X.com scraping skill, but it asks users to export live login cookies and uses authenticated X requests without enough safety guidance.

Install only if you intentionally want account-backed X.com scraping. Use a dedicated low-privilege account, keep exported cookies out of version control and shared folders, delete or rotate them after use, expect possible X.com enforcement or rate limits, and review the scripts before pointing them at valuable accounts or sensitive datasets.

SkillSpector

By NVIDIA

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
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands

Findings (12)

Lp3

Medium

Category: MCP Least Privilege
Confidence: 95% confidence
Finding: The skill documents code-driven capabilities to read and write local files and make network requests, but it does not declare any permissions or capability boundaries. In an agent setting, this weakens transparency and consent, making it easier for the skill to access local seed files, exported cookies, and remote X endpoints without an explicit permission model.

Context-Inappropriate Capability

Medium

Confidence: 97% confidence
Finding: The script embeds a hardcoded X/Twitter bearer token and combines it with imported browser cookies to perform authenticated GraphQL requests. This creates a credential-handling risk because anyone with access to the skill can reuse the token and session flow, and the skill normalizes unauthorized account-backed scraping rather than requiring explicit runtime-provided credentials and consent.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The README explicitly instructs users to export X.com login cookies, which are authentication secrets equivalent to a live session token. Without strong warnings about account takeover risk, secure handling, scope minimization, and storage hygiene, users may expose credentials to the skill, local files, logs, or third parties, enabling unauthorized account access.

Missing User Warnings

Medium

Confidence: 88% confidence
Finding: The README states that the skill uses real browser automation to bypass anti-scraping protections, but does not warn about legal, policy, detection, or account-enforcement risks. In the context of a scraping skill targeting X.com, omission of those warnings can mislead users into unsafe operation that may trigger account suspension, IP blocks, or other downstream consequences.

Missing User Warnings

Medium

Confidence: 94% confidence
Finding: The README instructs users to export and store live X.com login cookies, which are effectively bearer credentials, without warning that anyone who obtains them may gain account access until they expire or are revoked. In a scraping skill specifically designed to bypass platform protections, normalizing cookie export increases the chance of unsafe handling, accidental leakage, and privacy or account compromise.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: The skill instructs users to export X.com authentication cookies and reuse them for scraping, but gives no warning that these cookies are live session credentials. If mishandled, they can enable account takeover, unauthorized access, or reuse outside the intended scraping task.

Missing User Warnings

Medium

Confidence: 90% confidence
Finding: The skill is designed for large-scale tweet collection, GraphQL querying, and persistent local data merging, but it provides no privacy, retention, or terms-of-use warning. This can lead users to collect and store large volumes of public-but-sensitive data without understanding legal, policy, or downstream handling risks.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The workflow explicitly instructs users to export authenticated X.com cookies to a local file, which are effectively session credentials and can enable account takeover if exposed, reused, or mishandled. In a scraping skill, this is particularly sensitive because operators may share artifacts, commit files, or run on less-trusted machines, yet the document provides no warning, storage guidance, redaction, or disposal instructions.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: The script loads authentication cookies from disk and injects them into a browser context without any validation, minimization, or user-facing warning. In a skill context, this is sensitive because it silently uses bearer-like session material that can act with the user's authenticated X.com identity and exposes operators to credential misuse or accidental leakage through local file handling.

Missing User Warnings

Medium

Confidence: 87% confidence
Finding: The script performs authenticated requests to X.com using injected cookies with no explicit disclosure at runtime that it will contact the live service as the logged-in user. In an agent skill, undisclosed authenticated network activity is risky because it can surprise operators, trigger account actions, or expose private session context to a third-party platform under automation.

Missing User Warnings

Medium

Confidence: 91% confidence
Finding: The skill reads cookie data from disk and injects it directly into a browser context, enabling use of an existing authenticated session without any built-in user warning, confirmation, or safeguards around credential provenance. In a scraping skill, this is especially risky because it encourages handling live session secrets that could be misused, leaked from local storage, or applied to accounts without adequate authorization checks.

Missing User Warnings

Medium

Confidence: 89% confidence
Finding: The script issues authenticated GraphQL requests using a bearer token and CSRF token derived from loaded cookies, but provides no user-facing disclosure that account-backed requests will be sent to X APIs. This is dangerous because operators may unknowingly expose session-linked activity, trigger platform enforcement, or process data under an authenticated identity without informed consent.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

Detected: suspicious.exposed_secret_literal

File appears to expose a hardcoded API secret or token.

Critical

Code: suspicious.exposed_secret_literal
Location: scripts/scrape_x_v9.py:23