Back to skill

Security audit

uscis-case-status

Security checks for vulnerabilities and agentic risk

Overview

The skill is a straightforward wrapper for checking USCIS case status, with a disclosed but mutable third-party pip dependency users should treat cautiously.

Install only if you are comfortable running an externally maintained Python package that is not pinned in this skill. Use an isolated environment, avoid unnecessary credentials or browser profiles, and treat USCIS receipt numbers as sensitive personal information.

Vulnerability Patterns
  • Insecure DependenciesIntroduces malicious components through unsafe dependency sources
  • 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
Findings (1)

T08 · Insecure Dependencies

Warning
Location
SKILL.md:4
Finding

Unpinned and Unreviewable Third-Party Python Package Installation

Content
View full analysis
``` ``` ### Technical Analysis The skill directs the environment to install `uscis-case-status` through pip and then execute it as a Python module. The dependency is not constrained to an exact version, package hash, trusted index, or immutable artifact. The project contains only `SKILL.md`; consequently, neither the package implementation nor its transitive dependencies can be reviewed from the supplied artifact. Dependency resolution can therefore select whatever package release is current on the configured package index at installation time. This creates a mutable supply-chain boundary: a compromised maintainer account, malicious future release, package-index compromise, or dependency confusion caused by an untrusted index configuration could change the code executed without any modification to this skill. The package is subsequently invoked directly with `python3 -m uscis_case_status`. At that point, all package initialization and module code runs with the permissions and environmental access of the invoking agent. If pip resolves a source distribution, package build tooling may also execute code during the build process, depending on the package and installer configuration. This finding does not establish that the named package is currently malicious. It establishes that the skill executes an externally maintained, mutab ...[truncated 1544 chars]
Remediation
View remediation
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