Zshijie Publisher
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill matches its stated Z视介 publishing purpose, but it stores and reuses a login session and can publish or edit account content with limited guardrails.
Install only if you intend to let OpenClaw publish or edit Z视介 content. Before each publish or edit, review the exact JSON payload and target article_id, scan the QR code only for the intended account, prefer HTTPS/default trusted hosts, and delete the saved session file when finished.
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.
If the agent proceeds with a wrong JSON payload or article_id, it could publish incorrect content or edit existing content on the user's account.
These commands can create or modify Z视介 account content. The artifacts describe the execution path but do not require a final user confirmation, preview, or rollback plan before the mutating request is sent.
Build the exact request body as a JSON file matching the operation docs. Pass it with `--input-json`. Run one of `publish-article`, `edit-article`, `publish-video`, or `edit-video`.
Require an explicit user approval step showing the exact title, article_id, media URLs, and target operation before every publish or edit request.
A reusable login session could be exposed on the network or to an unintended endpoint, allowing actions as the logged-in Z视介 account.
The default publish/edit API sends a reusable login session token in both a header and Cookie to an HTTP endpoint, which is a sensitive account credential transport risk.
"base_url": "http://zugcpublish.cztv.com" ... "headers": { "sessionId": "{{sessionId}}", "Cookie": "sessionId={{sessionId}}" }Use HTTPS-only endpoints where possible, restrict or validate any base-url override, and warn the user before sending session cookies to any non-default host.
Anyone or any process that can read the session file may be able to reuse the logged-in account session until it expires or is revoked.
The skill stores and reuses a session credential for account actions, but the metadata declares no primary credential and the artifacts do not clearly define retention, cleanup, or file-permission expectations.
After scan success, extract `sessionId` from the QR polling response or `Set-Cookie` headers. Save it to the local session file. All publish and edit operations send the `sessionId` request header and also keep `Cookie: sessionId=...` for compatibility.
Store the session file in a user-private location with restrictive permissions, document how to delete or rotate it, and disclose the credential requirement in metadata.