rodin3d-skill
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill mostly matches its 3D-generation purpose, but its downloader can write provider-named files without safely constraining the path, and users should review its API-key and third-party upload behavior.
Before installing or using this skill, be comfortable sending selected images or prompts to Hyper3D. Use a protected API key, avoid echoing it or passing it directly on the command line, and run the scripts in a virtual environment. Until the download path handling is fixed, use a dedicated empty output folder and inspect downloaded filenames carefully.
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 malicious or malformed download response could cause the skill to overwrite or create files outside the folder the user chose for generated models.
The filename is taken from the provider response and joined directly with the output directory before writing. If the filename contains path separators, `..`, or an absolute path, the write may escape the intended output directory.
download_model(file_info.get('url'), task_output_dir, file_info.get('name')) ... output_path = os.path.join(output_dir, filename) ... with open(output_path, "wb") as f:Sanitize downloaded filenames with `os.path.basename`, reject absolute paths and `..`, and verify the resolved output path stays inside the chosen output directory before writing.
Your Hyper3D API key could be revealed to anyone who can see the terminal transcript, command history, or running process arguments.
The skill needs a Hyper3D API key, which is expected for this provider integration, but the documented checks and command-line usage can expose the key in terminal output, logs, shell history, or process listings.
echo $HYPER3D_API_KEY ... --api-key $HYPER3D_API_KEY
Avoid echoing secrets. Prefer reading the key from a protected environment variable or secure secret store, and avoid passing real API keys directly as command-line arguments when possible.
Images, prompts, and generation settings submitted through the skill are sent to Hyper3D, so private or sensitive assets may leave your local environment.
The client posts selected image files and generation parameters to Hyper3D's external API. This is disclosed and purpose-aligned, but it is still a third-party data transfer.
self.api_url = "https://api.hyper3d.com/api/v2/rodin" ... requests.post(self.api_url, headers=self.headers, files=files, data=data, timeout=300)
Only submit images and prompts you are allowed to share with Hyper3D, and review the provider's privacy and retention terms before using confidential content.
Different installs may use different dependency versions, which can affect reliability or expose users to newly introduced package vulnerabilities.
The Python dependencies are not version-pinned. They are common packages and no hidden installer is shown, but the resolved versions may vary across installations.
requests Pillow
Install in a virtual environment and consider pinning known-good versions with hashes or a lockfile.