golang-samber-hot

• Outcome: Pass
• Latest audit: Sep 15, 2026 · 12:57 AM UTC
• Version: 1.1.0

Overview

This skill is a coherent Go caching guide with one supply-chain hygiene note around its unpinned dependency install command.

Before installing or following the setup command, prefer a pinned command such as `go get github.com/samber/hot@vX.Y.Z`, review the resulting `go.mod` and `go.sum` changes, and run normal Go dependency checks. The skill otherwise reads as a focused coding guide for samber/hot caching.

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:36

Finding

Unpinned Dependency Upgrade Introduces Supply-Chain Risk

Content

View full analysis

Vulnerability Details

File Location: SKILL.md, lines 36–38
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: Medium

Vulnerable Code

bash

go get -u github.com/samber/hot

Technical Analysis

The installation guidance uses go get -u without specifying an audited module version. This resolves a mutable upstream release and may also upgrade related dependencies. Consequently, users executing the documented command can import code that differs from the code originally reviewed with this skill.

The module path points to the official github.com/samber/hot project, and the audited files contain no evidence that the current upstream package is malicious. The risk arises from automatically trusting future upstream releases and transitive dependency updates rather than pinning a reviewed version.

Attack Path

1. An attacker compromises the upstream module repository, a maintainer account, or a relevant transitive dependency.
2. The attacker publishes a malicious or backdoored release.
3. A user follows the skill’s installation command.
4. go get -u resolves the mutable release and may upgrade related modules.
5. The malicious dependency enters the user’s go.mod and go.sum.
6. Its code executes when the affected package is built, tested, or used at runtime.

Impact Assessment

Successful exploitation could execute code with the privileges of the developer, CI worker, build environment, or deployed service using the dependency. Depending on that environment, the affected code could access source code, build credentials, environment variables, network resources, application data, and other resources available to the process.

The scope is limited by the privileges and isolation controls of the environment in which the dependency is built or run.

Remediation

View remediation

Remediation Suggestions

• Replace the mutable upgrade command with an explicitly reviewed version:

bash

go get github.com/samber/hot@vX.Y.Z

• Remove -u so installation does not implicitly upgrade unrelated direct or transitive dependencies.
• Commit and verify go.mod and go.sum.
• Review dependency diffs before approving updates.
• Use automated vulnerability and provenance checks in CI, such as govulncheck, dependency review, and release-signature or source-verification controls where available.
• Perform dependency upgrades through a controlled update process with testing and rollback support.

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

Static analysis

No suspicious patterns detected.