Skill flagged — suspicious patterns detected

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

Docx Cn 1.0.1

v1.0.0

Word 文档处理 | Word Document Processing. 创建、读取、编辑 Word 文档 | Create, read, edit Word documents. 支持 .docx 格式、格式化、表格、图片 | Supports .docx format, formatting, tables...

0· 86·2 current·2 all-time
byBeta@binbin
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, SKILL.md, and included Python scripts all focus on creating, reading, editing, and validating .docx/.pptx/.xlsx files — this aligns with the stated purpose. However, the skill fails to declare several required external tools and binaries (soffice/LibreOffice, pandoc, npm docx package, pdftoppm, and gcc for the shim) even though both SKILL.md and the code expect them. That mismatch is unexpected and should be remedied or called out to users.
!
Instruction Scope
Runtime instructions (SKILL.md) and the included scripts operate on user-supplied Office files and unpacked directories (expected). But the code also: (1) writes a LibreOffice macro into a user profile directory and invokes soffice to execute it; (2) may compile and LD_PRELOAD a C shim at runtime to work around AF_UNIX socket restrictions. Both actions go beyond simple file-editing guidance and introduce behavior that affects the runtime environment and executes compiled native code.
Install Mechanism
There is no install spec (no external downloads), which keeps install risk low. However, the included office/soffice module generates C source into the temp directory and invokes gcc to build a shared object at runtime, then uses LD_PRELOAD. Runtime compilation/execution of native code is higher risk than pure Python/JS and should be considered carefully.
Credentials
The skill does not request any environment variables, credentials, or external config paths in its metadata. The file operations and temp-file usage in the scripts are proportionate to document processing. Still, the skill writes to /tmp (e.g., macro profile, compiled shim) and sets LD_PRELOAD for subprocesses it launches; those are environment-affecting actions that are not reflected in the declared requirements.
Persistence & Privilege
always:false and no cross-skill configuration changes. The skill does create files under /tmp (a LibreOffice profile path and a compiled .so shim) and writes a LibreOffice macro into that profile; these artifacts can persist across runs until cleaned and could affect subsequent LibreOffice invocations if reused. This is not permanent system-wide installation but is more than ephemeral in-memory activity.
What to consider before installing
This skill appears to actually implement .docx/.pptx/.xlsx unpacking, editing, validation, and packing — that part is coherent. Before installing or running it, consider: - Required tools: The skill expects LibreOffice (soffice), pandoc, pdftoppm, the docx npm package (docx-js), and gcc — but the skill metadata declares no required binaries. Ensure you only run it on machines where you trust those tools and understand they will be invoked. - Runtime compilation & LD_PRELOAD: The soffice helper writes a small C source file to the temp directory, compiles a shared object with gcc, and uses LD_PRELOAD for a socket shim. Compiling and preloading native code at runtime raises risk (can execute native operations and affect process behavior). If you don't want that, avoid using the functions that trigger the shim or run in an environment where AF_UNIX works so the shim isn't needed. - LibreOffice macro: The skill writes a StarBasic macro into a LibreOffice profile under /tmp to accept tracked changes and then calls soffice to run it. Macros can execute actions within LibreOffice; inspect the macro (it's visible in the repository) and run in an isolated environment if you have sensitive files. - Run in a sandbox: Test the skill on non-sensitive documents in an isolated environment (VM or container) first. Check that the temp files (/tmp/libreoffice_docx_profile and the compiled lo_socket_shim.so) are acceptable for your security posture and are removed if desired. - Verify provenance: The LICENSE states Anthropic but the source/homepage are unknown and owner metadata doesn't match that license header; consider whether you trust this package origin before use. If you need to proceed: review the soffice shim source and the macro content, confirm which external binaries will be invoked, and prefer running these scripts in a disposable environment (or adapt them to avoid runtime compilation and macro writes).

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

latestvk975wthynyfmpv6vnc9wxavmds83av7e

License

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

Runtime requirements

📄 Clawdis

Comments