Back to skill

Security audit

Receivable Aging Analyzer

Security checks for vulnerabilities and agentic risk

Overview

This skill gives local, informational accounts-receivable guidance and does not show hidden execution, network access, credential use, persistence, or transaction capability.

Before installing, treat this as a lightweight informational AR-aging helper, not professional financial, tax, legal, or collections advice. The publisher should narrow the trigger phrases and clarify language behavior, but the inspected artifact does not show hidden access or unsafe system behavior.

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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (8)

Vague Triggers

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The trigger section is materially broader than the stated purpose of a receivables-aging skill, inviting use for unrelated financial advice such as budgeting, tax deductions, pricing, and general financial health. In an agent environment, this scope confusion can cause incorrect skill selection, unsafe overreach into higher-risk financial guidance, and user reliance on outputs that are outside the skill’s claimed expertise and safeguards.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The README mixes English headings with core descriptive and example content written in Chinese, but does not state that the skill is Chinese-only or offer an alternative language option. This can violate language/locale policy when a skill implicitly requires a specific language without user opt-in.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
86% confidence
Finding

The file includes a scenario and expected output entirely in Chinese, but the skill does not state any language-selection behavior or user opt-in mechanism. This can create a language/locale policy issue because the skill appears to prescribe a specific output language in at least one usage path without clarifying that the response should follow the user's preferred language.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The module docstring says the skill is a descriptive provider of templates and frameworks, suggesting generic non-analytic behavior. In practice, the code parses financial terms, extracts amounts and dates, classifies urgency/timeframe, and generates receivable-aging-specific recommendations, which is materially more specific than the stated description.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger list includes very generic terms such as "receivable," "aging," and "analyzer," which are likely to appear in ordinary finance conversations unrelated to this specific skill. This can cause unintentional invocation or routing collisions, leading the agent to activate the wrong skill and produce unintended finance guidance or workflow behavior.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
96% confidence
Finding

Line L18 states 'Clear documentation in English,' which imposes a language requirement in natural language. Under the policy, forcing a specific language without user opt-in or a documented justification is a locale/language policy violation.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Low
Category
Not specified by scanner
Confidence
80% confidence
Finding

While the code does not call external APIs or perform transactions, the phrase 'No real code execution' contradicts the actual behavior because the file does execute parsing and analysis logic over user input. This is not merely omitted detail; the documentation expressly minimizes behavior that the code clearly performs.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

The manifest explicitly sets the skill language to "en," which can be interpreted as enforcing a specific language or locale. There is no accompanying indication that users may choose another language or that English-only behavior is required for a justified region-specific purpose.

Content

No source excerpt is available for this finding.