Security audit

Business Income Tracker

Security checks for vulnerabilities and agentic risk

Overview

This income-tracking skill is simple and not malicious, but it should be reviewed because it processes sensitive financial records with broad triggers and unclear scheduled-check instructions.

Before installing, treat this as a financial-data helper: avoid entering account numbers, credentials, tax identifiers, or unnecessary sensitive details, and only enable any daily check after deciding exactly what records it may access and how it can be turned off.

A.I.G

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

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (8)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: This skill is designed to handle income, expenses, expected revenue, and payment records, all of which are sensitive financial data, but it provides no warning, minimization guidance, or privacy handling expectations. Users may disclose detailed personal or business financial information without understanding the sensitivity or retention implications, increasing confidentiality and privacy risk.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: The trigger phrases are generic finance terms such as income tracking, expense records, ROI calculation, and income statistics, which can easily appear in ordinary conversations. This increases the chance of unintended activation in contexts where the user did not explicitly request this skill, potentially causing unsolicited collection or structuring of sensitive financial information.
Content: No source excerpt is available for this finding.

Vague Triggers

Medium

Category: Not specified by scanner
Confidence: 90% confidence
Finding: The automatic activation condition 'daily 09:00 automatic check (manual automation)' is ambiguous and does not define scope, consent, or what data source is being checked. In a finance context, unclear automation can lead to unexpected processing of sensitive income and expense data without an explicit user action at the time of execution.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: This markdown file presents all user-facing content exclusively in Chinese, which can violate language/locale policy when no user opt-in or alternative language is provided. The file does not indicate that the skill is region-specific or that Chinese is an intentional, documented locale constraint.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 93% confidence
Finding: The file title and all operational instructions are presented in Chinese only (e.g. '使用说明', '快速开始'), which imposes a specific language on users. The policy allows locale constraints only when users are given a choice or the restriction is clearly justified, neither of which appears here.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 96% confidence
Finding: The entire skill description and output format are presented only in Chinese, with no indication that users may choose another language or locale. Under the policy, a fixed language without opt-in can be a natural-language policy violation unless the locale restriction is explicitly justified.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 89% confidence
Finding: The markdown template is entirely written in Chinese, including headings and table labels, with no indication that language selection is optional or that the template is intended only for a Chinese-speaking or region-specific context. Under the policy scope provided, this is a natural-language locale constraint that should be either optional or clearly justified.
Content: No source excerpt is available for this finding.

Natural-Language Policy Violations

Low

Category: Not specified by scanner
Confidence: 91% confidence
Finding: This code emits user-facing output in Chinese (收入, 支出) with no indication that the skill is region-specific or that users can choose a language. That creates a natural-language locale policy concern because the skill imposes a specific language without opt-in.
Content: No source excerpt is available for this finding.