T09 · Insecure Skill Coding Practices
Warning
- Location
SKILL.md:23- Finding
Plaintext Persistence of Sensitive Resume Profile Data
- Content
View full analysis
- Remediation
View remediation
Security audit
Resume JD Match — JD定制简历
Security checks for vulnerabilities and agentic risk
Overview
This resume skill is useful and mostly purpose-aligned, but it stores sensitive personal profile data in a plaintext workspace file and its security description understates where it writes data.
Review before installing if you are comfortable storing resume details, contact information, and possibly birth date in a plaintext workspace file. Use it only in a private workspace, avoid committing generated profile or resume files, and inspect generated HTML before opening or sharing it.
Vulnerability Patterns
- Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
- Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
- Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
- Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
- Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (2)
T09 · Insecure Skill Coding Practices
Warning
- Location
SKILL.md:38- Finding
Untrusted Resume and Job Description Fields May Be Embedded into HTML Without Escaping
- Content
View full analysis
[Name] - [Job Title] /* see CSS below */- Remediation
View remediation
`, raw CSS, script, or attribute contexts. 7. Validate accent-color input against a strict grammar, such as six-digit hexadecimal color values, rather than accepting arbitrary CSS. 8. Add a Content Security Policy that blocks scripts, plugins, frames, and remote resources. For a self-contained resume, use a policy such as `default-src 'none'; style-src 'unsafe-inline'; img-src data:`. 9. Configure the PDF renderer with network access disabled and local-file access restricted to the generated document and explicitly required assets. 10. Add tests using payloads containing closing tags, event handlers, malicious links, remote images, and CSS injection to verify that they appear only as inert text. ]]>
Vulnerability Patterns
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
- Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
- Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
- Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)
Hidden Instructions
High
- Category
- Prompt Injection
- Confidence
- 70% confidence
- Finding
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
- Content
md </head> <body> <div class="resume"> <div class="header"> <!-- Name, target, contact --> <div class="section edu"> <!-- Education (brief, near top) --> <div class="section"> <!-- 3 Core Advantages grid --> <div class="section"> <!-- Key Projects -->
Vague Triggers
Medium
- Category
- Not specified by scanner
- Confidence
- 94% confidence
- Finding
The 'Use when' section includes broad phrases like 'make me a resume' and 'customize resume for this job', which can overlap with common user requests and may cause unintended invocation. The description does not provide explicit exclusion conditions or narrower trigger boundaries to distinguish when this skill should or should not activate.
- Content