T01 · Skill Instruction Hijacking
- Location
SKILL.md:65- Finding
Skill Rules Attempt to Override All Other Instructions
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly fits a job-search tool, but it needs Review because it can auto-install a global package, overstates its instruction priority, and under-discloses credential and network handling.
Install only if you are comfortable with a job-search tool reading your resume/profile, writing .careerclaw tracking files, contacting RemoteOK and Hacker News, and, for Pro, sending license validation to Gumroad and draft context to your configured LLM provider. Before routine use, require explicit approval for any global npm install, avoid running the debug license scripts with real keys, and treat generated outreach from public job listings as something to review before sending.
SKILL.md:65Skill Rules Attempt to Override All Other Instructions
scripts/debug_license.ts:10Debug Scripts Print the Complete Pro License Key
src/license.ts:96Raw Pro License Key Is Sent to an Undisclosed Gumroad Endpoint
SKILL.md:52Skill Automatically Performs a Global npm Installation
src/llm-enhance.ts:232Untrusted Job Listing Fields Are Embedded Directly into LLM Instructions
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
vitest 2.1.9 is reported as vulnerable to arbitrary file read and execution issues in specific testing/UI-related contexts. Because this is a devDependency, the risk is mainly during local development or CI when Vitest UI/server features are enabled, but compromise in those environments can still expose source code, secrets, or build agents.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
If the package includes outbound LLM request behavior and privacy-related test/exercise paths while the skill only lightly mentions optional API keys, users may not appreciate that resume-derived content could be sent to third-party model providers. Given the sensitivity of career data, incomplete disclosure raises privacy risk even if the behavior is feature-related rather than malicious.
Dependency has known vulnerabilities (CVEs). Using packages with unpatched security flaws exposes the environment to known exploits.
fast-xml-builder is a runtime dependency of fast-xml-parser, and the advisory indicates malformed attribute encoding can allow malicious content to bypass intended sanitization during XML generation. In a job-search skill that may transform or emit XML-like content from external feeds or user-controlled profile/job data, this could enable injection into downstream consumers or corrupted structured output.
fast-xml-parser is a direct runtime dependency, making its XML entity expansion and builder injection advisories relevant to the deployed skill. Since a career-search tool may ingest third-party job feeds, resumes, or syndication data in XML, maliciously crafted input could trigger denial of service or content injection during parse/build operations.
Detected: suspicious.dangerous_exec