Security audit

Eternal Expense Tracker

Security checks for vulnerabilities and agentic risk

Overview

This is a local expense-tracking skill whose financial-data handling is expected and mostly disclosed, with privacy and export hardening gaps users should understand.

Install only if you are comfortable storing expense records, receipt details, merchant names, and imported bank-statement rows locally under ~/.expense-tracker/. Use a private machine/account, review exported CSVs before opening them in spreadsheet software, and prefer pinned/trusted dependency installation if you enable OCR scanning.

A.I.G

Vulnerability Patterns

Insecure DependenciesIntroduces malicious components through unsafe dependency sources
Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
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

Findings (3)

T09 · Insecure Skill Coding Practices

Warning

Location: scripts/expense.py:309
Finding: Spreadsheet Formula Injection in CSV Exports
Content: View full analysis
Remediation: View remediation

T09 · Insecure Skill Coding Practices

Note

Location: scripts/expense.py:28
Finding: Sensitive Financial Data Stored Without Explicit Restrictive Permissions
Content: View full analysis
Remediation: View remediation

T08 · Insecure Dependencies

Note

Location: scripts/expense.py:106
Finding: Unpinned Runtime Dependency Installation Guidance
Content: View full analysis
Remediation: View remediation

SkillSpector

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

Findings (3)

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: The skill explicitly handles receipt images and bank statement imports, and it states that all data is stored in ~/.expense-tracker/, but it does not warn users that these inputs contain sensitive financial information. This can lead users to unknowingly retain unencrypted personal spending data, merchant history, and account-related records on disk, increasing privacy and disclosure risk on shared or compromised systems.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 94% confidence
Finding: When scan extracts receipt items, it automatically converts them into transactions and writes them to the tracker file. Although the function prints extracted text and final success output, there is no user-facing warning or confirmation that potentially sensitive receipt contents will be persisted as expense records.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 89% confidence
Finding: The import command reads a bank statement CSV and appends all rows into transactions.json, which is a safety-relevant file write involving sensitive financial data. The code reports success afterward, but it does not give a prior warning, confirmation, or clear user disclosure in the command help/docstring that imported financial records will be stored persistently under ~/.expense-tracker/.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.