T08 · Insecure Dependencies
- Location
SKILL.md:85- Finding
Unpinned Dependency Installation Into the System Python Environment
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
Plutus Pro is a local expense-analysis skill, but it automatically saves detailed financial reports and recommends a risky system Python install, so users should review it carefully before installing.
Install only if you are comfortable with the skill writing detailed financial reports into the working directory. Use a private folder, avoid shared or synced directories, review generated files before sharing or committing anything, and consider using an isolated Python virtual environment instead of the documented system pip command.
SKILL.md:85Unpinned Dependency Installation Into the System Python Environment
SKILL.md:371Sensitive Financial Records Exported to Predictable Plaintext Files
The skill exports detailed transaction data, including dates, descriptions, amounts, categories, and tax flags, into markdown, CSV, and JSON files without prominent upfront warning or explicit consent. In a finance context this is highly sensitive information, and persistent local copies materially increase privacy and confidentiality risk, especially on shared machines or synced workspaces.
The skill presents itself as an expense-analysis tool for CSV/text inputs, but the implementation also writes markdown, CSV, and JSON reports containing potentially sensitive financial data to local disk. That side effect is security-relevant because users may not expect persistent storage of transaction details, which increases exposure to other local users, backup systems, sync tools, or later exfiltration by unrelated software.
The manifest and README-style content describe setup and then say simply 'Run — you're in' without any explicit trigger phrases, invocation constraints, or negative examples. For a markdown skill file, this leaves activation scope ambiguous and could lead to unintended use for loosely related finance requests.
The skill's stated purpose is wealth/expense analysis, but the documentation and code add a commercial gating capability requiring a paid license key and directing users to purchase links. This is not part of the analytical function itself and is an unrelated capability from the perspective of the skill's declared purpose.
Accessing LICENSE_KEY is not an obvious requirement for expense categorisation, forecasting, tax tagging, or report generation. With no separate declared purpose for authentication or licensing, this environment access is ancillary commercial-control behavior rather than core skill functionality.
No suspicious patterns detected.