X Media Parser
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The main X/Twitter media parsing purpose is coherent, but the included scripts contain an unsafe URL-to-Python interpolation and a one-click downloader that uses a hardcoded Aria2 host/token.
Review and fix the shell scripts before installing. The basic vxtwitter parsing behavior is expected, but avoid using the included commands with untrusted URLs, and do not run the Aria2 downloader unless the RPC endpoint, token, and download directory are changed to your own explicit configuration.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A maliciously crafted URL could cause code to run under the user's agent account when the parser is invoked.
The first argument is interpolated directly into Python source code passed to python3 -c. A crafted URL containing quotes or Python expression syntax could change what the Python interpreter executes.
URL="$1" ... curl -s "https://api.vxtwitter.com/Twitter/status/${TWEET_ID}" | python3 -c " ... 'url': '$URL',Do not embed raw shell variables into Python source. Pass the URL as an argv/env value, JSON-escape it, or strictly validate it before use.
Running the helper may queue downloads and write files on an unexpected Aria2 service on the local network.
The one-click downloader posts aria2.addUri requests to a hardcoded RPC endpoint, token, and directory rather than a user-confirmed or documented configuration.
rpc_url = 'http://10.0.0.1:6800/jsonrpc' secret = '88888888' dir_path = '/mnt/sda1/download/X' ... result = subprocess.run(['curl', '-s', '-X', 'POST', rpc_url, ...])
Make the Aria2 endpoint, secret, and directory explicit user configuration, display them before use, and require confirmation before adding downloads.
The skill can use an undeclared embedded credential to control an Aria2 instance, rather than relying on credentials the user knowingly provides.
Although the shell wrapper appears to allow an ARIA2_SECRET environment variable, the Python block ignores it and uses a static embedded RPC token to authorize Aria2 actions.
SECRET="${ARIA2_SECRET:-}"
...
secret = '88888888'
...
params = [f"token:{secret}", [url], {"max-connection-per-server": 16, ...}]Remove the hardcoded token, declare the Aria2 credential requirement, and require the user to supply the secret through a documented configuration path.
It is harder to verify the origin of the scripts or know exactly how they are intended to be installed and invoked.
The artifact provides a generic homepage, unknown source, and no declarative install mapping for the included shell scripts, which weakens provenance and setup clarity.
Source: unknown Homepage: https://github.com No install spec — this is an instruction-only skill.
Provide an exact repository URL, a clear install spec, and declare required local binaries such as curl and python3.