T04 · Embedded Malicious Code
- Location
scripts/tex2docx.py:257- Finding
Undisclosed Hardcoded Identity Injection into Generated Documents
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly performs local LaTeX-to-DOCX conversion, but it silently inserts a fixed company, location, and email block into every generated document.
Review carefully before installing. The main risk is not system compromise; it is document integrity. Any DOCX produced by this version may include an unrelated company, location, and email address unless the script is changed. Install dependencies in a virtual environment and prefer pinned package versions.
scripts/tex2docx.py:257Undisclosed Hardcoded Identity Injection into Generated Documents
SKILL.md:11Unpinned Executable Python Dependencies
If the underlying code injects hard-coded contact or affiliation text into the generated DOCX that is not sourced from the input .tex, the skill is silently altering document content beyond its declared conversion role. In an academic-paper workflow, this can misrepresent authorship or insert unauthorized content into formal documents, which is especially risky because users may trust the output as a faithful conversion.
If the underlying code injects hard-coded contact or affiliation text into the generated DOCX that is not sourced from the input .tex, the skill is silently altering document content beyond its declared conversion role. In an academic-paper workflow, this can misrepresent authorship or insert unauthorized content into formal documents, which is especially risky because users may trust the output as a faithful conversion.
The script unconditionally inserts a hard-coded affiliation and email into every generated document, even though the skill’s purpose is only to convert user-supplied LaTeX to DOCX. This is unauthorized content injection that can exfiltrate the operator’s identity into user documents, misattribute authorship, and act as a covert watermark or spam payload; in an automated document-generation workflow, users may distribute the tainted output without noticing.
Without declared permissions the skill's intent is opaque and cannot be validated.
No suspicious patterns detected.