Back to skill

Security audit

xinjianxue-skill-roommate-cn

Security checks for vulnerabilities and agentic risk

Overview

The skill is transparent about using an external paid API, but it asks for and transmits sensitive birth, gender, and location details that are not well-justified for roommate advice.

Review this carefully before installing. Use it only if you are comfortable sharing birth, gender, and location details with the Xinjianxue service and linking the AI to your account. Do not provide another person's details unless they have clearly agreed, and prefer ordinary local roommate advice when you do not need the external report.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • 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 (1)

T05 · Unauthorized Access and Privilege Escalation

Warning
Location
SKILL.md:68
Finding

Excessive Personal Data Collection for Roommate Advice

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 68 and 199-202
Vulnerability Type: Excessive collection and external transmission of personal data
Risk Level: Medium

Evidence

The relevant source text, translated into English, states:

markdown
Before starting: When this service API is invoked, personal information about
the subject—including date of birth (and time), gender, place of birth, and
current location—is sent to the Xinjianxue API
(`chinaapi.xinjianxue.com`) for processing.
markdown
- Complete input: subject's date and time of birth, gender, place of birth
  (country and province/region/city), and current location.
- Basic input: subject's date of birth, gender, and current location.
- Both input levels require gender, date of birth, and the subject's current
  location (country and province/region/city).
- Complete input additionally requires exact birth hour and minute and place
  of birth (country and province/region/city).

Technical Analysis

The Skill provides guidance about roommate communication, boundaries, household rules, and conflict resolution. These functions do not inherently require a subject's date of birth, gender, birthplace, birth time, or current geographic location.

Nevertheless, the Skill requires several of these attributes before calling an external report service. This violates the data-minimization and least-privilege principles by obtaining and transmitting personal information beyond what is reasonably necessary for the declared task. The disclosure and consent language reduces the risk of covert collection, but it does not establish why every mandatory field is proportionate or technically necessary.

The Skill also permits analysis of another person when the user claims that person consented. No mechanism directly verifies the other person's identity or consent, creating a risk that a user could submit a roommate's information ...[truncated 1430 chars]

Remediation
View remediation

Remediation Suggestions

  1. Provide ordinary roommate communication and boundary-setting advice locally without collecting demographic or location information.
  2. Make the external report an optional feature rather than a prerequisite for receiving roommate advice.
  3. Explain separately why each requested field is needed, how it affects the report, and whether the service can operate without it.
  4. Remove mandatory collection of exact birth time, birthplace, gender, and precise current location unless necessity is documented and technically enforced.
  5. Use coarse location information where location is genuinely required, and avoid collecting province or city data by default.
  6. Obtain explicit, purpose-specific consent immediately before transmitting information to the external service.
  7. Do not submit another person's data based solely on an unverifiable assertion of consent. Prefer direct participation or independently recorded consent from each subject.
  8. Publish and technically enforce retention, deletion, access-control, and incident-response policies for submitted reports and request metadata.
  9. Ensure logs, telemetry, error responses, and conversation history do not retain birth details, location data, authorization codes, license keys, or API keys.
  10. Add a local fallback path when the user declines external processing or provides only the information necessary to describe the roommate conflict.
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep