Back to skill

Security audit

Rocom

Security checks for vulnerabilities and agentic risk

Overview

This is a local, read-only game data lookup skill with no evidence of network access, credential use, persistence, or unsafe behavior.

Install this only if you want Chinese Roco Kingdom:World reference data available locally. Expect it to require Node.js and read its bundled JSON files; I found no evidence that it sends data out or changes your system.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • 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
Findings (11)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

This JSON dataset is entirely written in Chinese field names and descriptions, with no indication that language is configurable or that the content is intended only for Chinese-speaking users. Under the stated policy, forcing a specific language or locale without user choice is a natural-language policy concern even in non-markdown/config content.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The skill data is entirely encoded in Chinese natural-language fields such as names and effect descriptions, with no accompanying indication that the skill is region-specific or that users may choose another language. Under the stated policy, forcing a specific language/locale without opt-in or justification is a natural-language policy issue.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
76% confidence
Finding

The manifest description states the skill is a general 'offline data tool' but does not define when the skill should activate, which phrases should invoke it, or any exclusion conditions. In manifest/markdown contexts, this lack of trigger specificity can make routing ambiguous if an agent relies on descriptive text for invocation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

This manifest-style JSON file stores all user-facing field names and descriptions exclusively in Chinese, with no indication that the skill is region-specific or that users can opt into this locale. Under the language/locale policy rule, fixed locale content without documented choice or justification can be a natural-language policy violation.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

This JSON file uses only Chinese-language values for both pageName and name, and there is no accompanying indication in the file that users may choose another language or that the content is intentionally limited to a Chinese-only locale. Under the natural-language policy rule, a file that imposes a single language without opt-in or justification can be considered a locale policy concern.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
77% confidence
Finding

This JSON data file contains user-facing natural-language fields such as titles, intros, author names, and member names entirely in Chinese, with no indication that the skill supports other languages or that Chinese is an explicitly justified locale requirement. Under the policy rule for natural-language violations, a file that effectively enforces a single language without opt-in can be flagged when no user choice or rationale is documented.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

SQP-3 applies to all file types and covers language or locale policy violations expressed in natural-language content. This file contains user-facing names and descriptors exclusively in Chinese throughout, but provides no surrounding indication that the locale is optional or intentionally limited to a China-specific context.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
94% confidence
Finding

This JSON dataset uses only Chinese field names and Chinese entity values throughout, with no accompanying indication that the skill is intentionally region-specific or that users can choose another language/locale. Under the policy, hard-coding a single language without opt-in can be a natural-language policy violation when no justification is documented in the file.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
83% confidence
Finding

This JSON file stores all user-facing task fields such as names, types, goals, and descriptions exclusively in Chinese. Under the policy rule for natural-language constraints, this can be a locale/language restriction because no opt-in, alternative locale, or justification is provided anywhere in the file.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

This JSON file uses Chinese-only field names and natural-language descriptions throughout, with no indication that the locale is optional or region-specific. Under the policy rule for natural-language violations, forcing a specific language without user opt-in can be a locale policy issue.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
98% confidence
Finding

This JSON file uses Chinese field names and Chinese-language skill names/effects throughout, with no indication that the content is optional, localized by user choice, or restricted to a Chinese-only deployment context. Under the policy, forcing a specific language or locale without user opt-in is a natural-language policy concern.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.