Back to skill

Security audit

Hash Generate

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed external hashing utility, but users should avoid sending secrets because inputs are processed by a third-party API.

Install only if you are comfortable with hash, HMAC, encode/decode, and hash-identification inputs being sent to hash.agentutil.net. Do not use it for passwords, API keys, private keys, recovery phrases, proprietary data, or other secrets unless you have explicitly decided remote processing is acceptable; prefer local tools for sensitive material.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • 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 (1)

External Transmission

Medium
Category
Data Exfiltration
Content
### Hash

```bash
curl -X POST https://hash.agentutil.net/v1/hash \
  -H "Content-Type: application/json" \
  -d '{"input": "hello world", "algorithm": "sha256"}'
```
Confidence
91% confidence
Finding
The skill explicitly sends user-provided input to an external third-party API for hashing. While this is part of the skill's stated functionality, it creates a real data exfiltration risk if users provide sensitive material such as passwords, API keys, tokens, or private keys; hashing/HMAC services are especially risky because users may submit secrets expecting local-only processing.

Static analysis

No suspicious patterns detected.