other
- Location
DAY2-REPORT.md:60- Finding
Instructions Solicit Disclosure of Reusable LLM API Credentials
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This resume skill is mostly purpose-aligned, but it includes unsafe instructions to send an API key to the publisher and has overbroad URL-fetching and auto-apply behavior that need review.
Install only if you are comfortable with a China-focused resume tool that reads your resume, may fetch JD URLs, and sends resume/JD excerpts to the LLM provider configured with your own key. Do not send API keys, payment screenshots, identity details, or real resumes over chat/private messages to the publisher; configure secrets locally and use sanitized samples where possible. Treat auto-apply as account-affecting automation and use it only with explicit review of each target and low limits.
DAY2-REPORT.md:60Instructions Solicit Disclosure of Reusable LLM API Credentials
lib/jd_fetcher.py:101Arbitrary JD URL Fetching Permits Server-Side Request Forgery
lib/license.py:27Public Default Secret Allows Forgery of Paid-Tier Licenses
The document explicitly asks the recipient to paste an LLM API key via private message, encouraging direct disclosure of a sensitive credential through an unsafe channel. API keys can be reused to access paid services, exfiltrate data, incur charges, and compromise any systems where the same operator uses the credential.
This is a direct natural-language prompt for the user to disclose an API secret ('把 sk-xxx 粘贴给我'), which normalizes credential sharing and creates a clear path for unauthorized use. In the context of an agent skill, this is especially dangerous because users may trust the workflow and reveal production keys that can be abused immediately.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
License generation, secret-based token creation, and admin CLI behavior are materially outside the user-facing purpose of resume rewriting. When such privileged or operational functionality is bundled into a consumer skill without clear disclosure, it expands the attack surface and raises the chance of misuse, secret mishandling, or unauthorized administrative actions.
The README documents an internal license-generation and order-management workflow that is unrelated to the declared resume-rewriting/job-application purpose of the skill. This mismatch is dangerous because hidden commercial-control or entitlement logic can indicate undisclosed functionality, broaden the attack surface, and enable misuse if the repository is granted access or distributed under false pretenses.
The documented ability to generate activation codes and maintain customer order records is not justified by the stated purpose of the skill, indicating hidden operational behavior beyond user expectations. In a skill ecosystem, undeclared capabilities are risky because they may conceal monetization controls, sensitive-data handling, or admin backdoors that reviewers and users would not anticipate.
The manifest advertises bulk customized auto-submission of resumes without any visible warning that personal data will be sent to third-party job platforms and that account-affecting actions may occur. Because resumes contain sensitive personal information and auto-apply changes the user's external account state, the lack of disclosure and safety constraints materially increases the risk of unauthorized data sharing, spam-like behavior, and platform-account penalties.
The substantive skill description in the changelog is entirely in Chinese, with no indication that users can choose another language or that the skill is intentionally limited to a Chinese-speaking or region-specific audience. Under the policy, forcing a specific language without opt-in is a natural-language locale violation.
The skill asks the user to provide an old resume as a test sample, and although it mentions that redaction is possible, it does not clearly warn against sharing sensitive personal data or set a privacy-safe default. Resumes commonly contain high-risk PII such as phone numbers, email addresses, addresses, work history, and identifiers, so this can lead to unnecessary collection or exposure of personal data during testing.
The document instructs the user to register a developer account, complete real-name verification, and bind an Alipay payout account without any safety, legitimacy, or privacy guidance. This can pressure users into submitting identity documents, biometric data, and financial account details to a third-party service without adequate validation of data handling risks.
Natural-language policy violations apply to all file types. The report content and the prescribed user replies are entirely in Chinese, with no indication that another language is supported or that the user can choose their preferred language.
The manifest describes a skill focused on rewriting resumes against a target JD and producing a rewritten resume, match score, and interview talking points. This report documents an additional auto_apply.py module for "Pro 批量投递", which is a separate job-application automation capability rather than an obvious implementation detail of resume optimization.
The marketing copy presents a contradictory claim: it says the tool is not a one-click auto-apply product, while elsewhere the paid tier includes Boss automatic delivery. This can mislead users, reviewers, or marketplaces about the actual automation behavior and safety profile, especially because auto-apply features carry platform-abuse, consent, and account-risk implications.
Claiming 'local-first' and 'resume data does not go to the cloud' while also sending content to third-party LLM providers is materially misleading if resume or JD text is included in prompts. This creates a privacy and compliance risk because users may expose sensitive personal and employment data under false assumptions about where their data is processed.
The text states '只测了中文简历,英文简历还没调', which communicates a language limitation without offering any user choice or opt-in path. Under the policy, language constraints should either be optional or clearly justified as region-specific; here it appears as a default product restriction in general marketing content.
The skill advertises capabilities that imply access to local files, network, environment variables, and possibly shell execution, but the manifest does not declare any tool scope or permissions boundaries. This weakens auditability and informed consent: users and the platform cannot easily tell what privileged operations the skill may perform, especially given the handling of resumes, payment/licensing, and optional auto-apply flows.
The manifest description presents the skill as a general-purpose resume rewriting and optional auto-application tool using broad natural language marketing copy, but it does not specify narrow trigger phrases, invocation boundaries, or exclusion conditions. In markdown/manifest scope, this can create ambiguous activation conditions because common job-seeking language could plausibly match the description without clear limits.
The quick-start section shows command usage, but the document never defines a precise set of activation phrases or non-activation cases in natural language. For markdown files, the absence of explicit trigger scope or exclusion examples makes invocation criteria ambiguous.
This file presents the skill content exclusively in Chinese, including headings, instructions, and pricing, with no indication that the user can opt into another language. Under the language/locale policy, forcing a specific language without user choice is a natural-language policy concern.
No suspicious patterns detected.