Vendor Compliance 1099

• Outcome: Pass
• Latest audit: Sep 12, 2026 · 6:24 AM UTC
• Version: 1.0.2

Overview

This is a coherent 1099 compliance skill, but it handles sensitive accounting data and users should secure the local cache and dependency setup.

Install and run this only in an accounting environment where QBO access is read-only and appropriate for the client. Treat `.cache/vendor-compliance-1099/` and generated workbooks as sensitive tax records, keep them out of source control and shared folders, and prefer a pinned dependency in a virtual environment.

A.I.G

Vulnerability Patterns

• Insecure Dependencies: Introduces malicious components through unsafe dependency sources
• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally

Findings (1)

T08 · Insecure Dependencies

Warning

• Location: SKILL.md:164

Finding

Unpinned Third-Party Python Dependency

Content

View full analysis

Vulnerability Details

File Location: SKILL.md, line 164
Vulnerability Type: Insecure third-party dependency installation
Risk Level: Medium

Vulnerable Code Snippet:

markdown

- **Python packages:** `pip install openpyxl`

Technical Analysis

The skill instructs users to install openpyxl without pinning a reviewed version or verifying the package artifact with cryptographic hashes. Consequently, dependency resolution is mutable: the version and artifact installed in the future may differ from those available when the skill was audited.

Python package installation may execute package build or installation logic with the privileges of the invoking user. If the named package, its distribution infrastructure, or a transitive dependency is compromised, following this instruction could introduce unreviewed code into an environment that handles QBO General Ledger and vendor compliance data.

The audit found no evidence that openpyxl is currently malicious. The issue is the unsafe, non-reproducible dependency installation practice.

Attack Path

1. An attacker compromises a future openpyxl release, a dependency, or the relevant package-distribution channel.
2. A user follows the instruction in SKILL.md and runs pip install openpyxl.
3. pip resolves and downloads the mutable, compromised artifact.
4. Malicious installation or runtime code executes under the user's account.
5. The code may access files, environment variables, QBO-related credentials, and accounting data available to that account.

Impact Assessment

Successful exploitation could permit arbitrary code execution with the privileges of the user performing the installation or running the pipeline. The accessible scope may include local financial workbooks, vendor records, W-9/TIN status files, QBO authentication material exposed to the process, and any other resources readable or writable by that user.

The referenced pip ...[truncated 234 chars]

Remediation

View remediation

Remediation Suggestions

• Pin openpyxl to a specifically reviewed version rather than allowing unconstrained resolution.
• Maintain dependencies in a lock file and require cryptographic hashes, such as by using pip install --require-hashes -r requirements.txt.
• Review and lock all transitive dependencies.
• Install dependencies inside a dedicated, least-privileged virtual environment.
• Use an approved package index or internally controlled mirror.
• Run dependency vulnerability and provenance checks in CI.
• Include the referenced pipeline in the package so its dependency use and sensitive-data handling can be audited.

SkillSpector

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Missing User Warnings

Medium

• Category: Not specified by scanner
• Confidence: 92% confidence

Finding

The skill handles and persists sensitive tax/compliance data, including vendor W-9 status, TIN status, and year-over-year payment snapshots, but the user-facing description and usage guidance do not prominently warn about local storage of this sensitive information. In an accounting/compliance context, this increases the risk of inadvertent exposure on shared workstations, unsecured home directories, backups, or source-controlled cache paths, especially because users may run it assuming it is only a transient reporting workflow.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.