Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

toutiao-publish-docx

v1.0.0

用 Cookie 或已保存会话在头条号后台发布文章,支持标题/正文/图片与固定目录 docx 导入。当用户要自动发头条文章、传入 cookie_header 或要求按 docx 流程发布时调用。

0· 41·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (publish to 头条 using cookie or saved session, support docx import) aligns with the runtime instructions (commands to run toutiao_poster). However the instructions assume a preexisting Python project and runtime environment at /home/ubuntu/projects/toutiao_poster and a module toutiao_poster; the registry metadata lists no required files or env vars, which is inconsistent with what the skill actually expects to run.
!
Instruction Scope
SKILL.md directs the agent to read and move files in fixed absolute paths (images/docx/artifacts under /home/ubuntu/projects/...), to save screenshots to those artifact directories, and to use a TOUTIAO_COOKIE environment variable. Those filesystem accesses and env-var usage are not declared and go beyond a simple API integration; the instructions assume local filesystem and session files exist and instruct modifying them (moving processed files to done/).
Install Mechanism
Instruction-only skill with no install spec and no code files — lowest install risk. Because it contains no packaged install steps, nothing would be written by the skill itself at install time. The runtime commands, however, assume existing installed code/software.
!
Credentials
Although the registry lists no required env vars, the SKILL.md shows use of TOUTIAO_COOKIE and allows overriding image/docx directories via env vars (TOUTIAO_IMAGE_DIR). Requesting and using cookies to authenticate is expected for this purpose, but the omission from declared requirements is an inconsistency. The skill will also read arbitrary files under the project path — access that could expose other artifacts if the environment is shared.
Persistence & Privilege
always is false and there is no indication the skill requests permanent or elevated platform privileges. It does instruct moving files under its own project directories, which is normal for a local automation script.
What to consider before installing
This skill appears to do what it says (automate publishing to Toutiao), but there are important mismatches you should address before installing or running it: - Missing declarations: SKILL.md uses the TOUTIAO_COOKIE environment variable and specific project paths (/home/ubuntu/projects/toutiao_poster and artifact directories), but the skill metadata lists no required env vars or config paths. Confirm where cookies/sessions will be stored and whether the platform will pass TOUTIAO_COOKIE if you provide one. - Verify the runtime environment: The instructions assume a Python project and virtualenv at /.venv and a module named toutiao_poster. If that code is not present on the host, the commands will fail. If it is present, inspect that code before running — it will have filesystem access to the referenced directories. - Protect secrets: A cookie header grants access to the user's account—only supply cookies you trust and only run this on a dedicated, non-shared environment. Do not paste browser cookies in untrusted consoles. - Filesystem risk: The skill reads/moves files under absolute paths. If you run it on a shared machine, ensure those paths don't contain unrelated sensitive data. Prefer running in an isolated VM/container with minimal other data. - Improve metadata before use: Ask the publisher to declare required env vars (TOUTIAO_COOKIE, optional TOUTIAO_IMAGE_DIR) and required config paths in the registry metadata so the permission surface is explicit. If you cannot verify the presence and content of the toutiao_poster project or cannot ensure a dedicated environment, avoid using this skill or run it only after code inspection and environment hardening.

Like a lobster shell, security has layers — review code before you run it.

latestvk974ha67ca0xe9j10qsma21eex83we6j

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments