Back to skill

Security audit

agent-bom runtime

Security checks for vulnerabilities and agentic risk

Overview

This skill is a coherent runtime-security monitoring helper, with the main caution that its documented package install is not pinned to the reviewed version.

Before installing, consider pinning the package to the reviewed version, such as `agent-bom==0.104.0`, and only configure ClickHouse or provide audit logs that you are comfortable analyzing with this tool.

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:49
Finding
Unpinned Third-Party Package Installation## Vulnerability Details **File Location**: `SKILL.md`, lines 49–53 **Vulnerability Type**: Unpinned third-party dependency installation **Risk Level**: Medium **Vulnerable Code Snippet**: ```markdown ## Install ```bash pipx install agent-bom ``` ``` ### Technical Analysis The installation command retrieves `agent-bom` from the configured Python package index without pinning its version or verifying an integrity hash. Although the skill metadata identifies version `0.104.0`, the documented command does not enforce that version. Consequently, the code installed by users may differ from the version reviewed when this skill was published. A compromised package-maintainer account, package-index compromise, or malicious future release could introduce attacker-controlled code. The package's implementation is not included in this project, so its advertised file, network, credential, and telemetry behavior cannot be independently verified from the audited artifact. ### Attack Path 1. An attacker compromises the `agent-bom` package, its maintainer account, or a transitive dependency. 2. The attacker publishes a malicious release to the package index used by the victim. 3. A user follows the documented `pipx install agent-bom` instruction. 4. The package manager resolves and installs the attacker-controlled release because no version or hash is enforced. 5. Malicious code executes during an applicable installation hook or when the installed application is invoked. 6. The payload accesses resources available to the installing user. ### Impact Assessment Successful exploitation could result in arbitrary code execution with the privileges of the user who installs or invokes the package. The affected scope may include that user's readable files, environment variables, application data, and available network resources. Higher impact is possible if installation or execution is performed from a privileged account, although the reviewed skill does not instruct users ...[truncated 22 chars]
Remediation
## Remediation Suggestions 1. Pin the package to the reviewed release: ```bash pipx install agent-bom==0.104.0 ``` 2. Provide a reproducible, reviewed dependency lock file covering transitive dependencies. 3. Publish and verify cryptographic hashes for all downloaded distributions where the installation workflow supports hash verification. 4. Document the trusted package index explicitly and prevent fallback to untrusted or unintended indexes. 5. Establish a release-review process that validates the pinned package artifact and dependency tree before updating the documented version. 6. Include or vendor the relevant source when feasible so the skill's claimed runtime behavior can be audited independently.
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

Static analysis

No suspicious patterns detected.